current shell's bash history lost on reboot
by Dusty Mabe
The other day during the Atomic Test Day jzb and I noticed that we
were losing bash history (seemingly randomly). Today I dug into it a
bit more. If you reboot a machine from a bash session then you will
lose all of your history for that session. Note the following is from
the F21 Cloud image:
[root@f21 ~]# cat .bash_history | wc -l
2
[root@f21 ~]# history | wc -l
123
[root@f21 ~]# reboot
Connection to 172.24.4.228 closed by remote host.
Connection to 172.24.4.228 closed.
[root@localhost ~(keystone_admin)]#
[root@localhost ~(keystone_admin)]# ssh -i key1.pem
fedora(a)172.24.4.228
Last login: Thu Nov 20 18:54:48 2014 from 172.24.4.225
[fedora@f21 ~]$
[fedora@f21 ~]$ sudo su -
[root@f21 ~]# history | wc -l
3
Has anyone else seen this? Is there an existing bug report?
If you guys can confirm you are having this behavior then I will open
a report. Alos please see [1] [2] where suse was having a similar problem.
Dusty
[1] - https://bugzilla.novell.com/show_bug.cgi?id=671719
[2] - https://bugzilla.novell.com/show_bug.cgi?id=652633
9 years, 3 months
[cloud] #74: Plan test days for Atomic image
by Fedora Cloud Trac Tickets
#74: Plan test days for Atomic image
--------------------+------------------------------
Reporter: jzb | Owner:
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Beta)
Component: --- | Keywords: meeting
--------------------+------------------------------
Once we have a viable image we need to go ahead and plan a test day around
the image (or more). We're still delayed on alpha, but all signs are
looking good for next week's go/no-go meeting.
Will set a date or dates and start working on promoting that. Setting
milestone as "beta" for this as it's something that should happen before
the beta, but after alpha...
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/74>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
9 years, 4 months
[cloud] #75: Article for Fedora Magazine on "state of cloud SIG/product" for alpha release
by Fedora Cloud Trac Tickets
#75: Article for Fedora Magazine on "state of cloud SIG/product" for alpha
release
----------------------------+-------------------------------
Reporter: jzb | Owner: jzb
Type: task | Status: new
Priority: normal | Milestone: Fedora 21 (Alpha)
Component: Website & Wiki | Keywords: meeting
----------------------------+-------------------------------
What it says on the tin - putting in a tracker ticket to work on this and
get it ready for the alpha release. Should go out simultaneously with the
alpha or maybe staggered by a day or two to keep interest high.
--
Ticket URL: <https://fedorahosted.org/cloud/ticket/75>
cloud <https://fedorahosted.org/cloud>
Fedora Cloud Working Group Ticketing System
9 years, 4 months
Meeting tomorrow - will we have a quorum?
by Joe Brockmeier
Hey all,
Past experience suggests that a lot of people fade out for vacation in
the U.S. early in the week. Wondering if we'll have a quorum (or
anybody) around for a meeting tomorrow?
(I've pinged a few folks on IRC and gotten no "ACKs" so my suspicion is
people are already on their way to family events.)
Best,
jzb
--
Joe Brockmeier | Principal Cloud & Storage Analyst
jzb(a)redhat.com | http://community.redhat.com/
Twitter: @jzb | http://dissociatedpress.net/
9 years, 4 months
Help to build a base Fedora Docker image
by Keith Sharp
I've been trying to get to grips with Docker over the last few days, and as learning exercise I've been trying to build a chain of images from scratch, however I've run into some problems and I hope someone can put me on the right track.
I working in a VM running Fedora 21 Beta Server, fully up to date. My Docker version is docker-io 1.3.2-2.fc21.
The steps I've taken are:
1) Downloaded Fedora-Docker-Base-20141029-21_Beta.x86_64.tar.gz to a directory called fedora and created a file in that directory called Dockerfile with only three lines:
FROM scratch
MAINTAINER Keith Sharp <kms(a)passback.co.uk>
ADD Fedora-Docker-Base-20141029-21_Beta.x86_64.tar.gz /
2) Used the docker command to build a new image:
$ sudo docker build -t passback/fedora:21beta .
Sending build context to Docker daemon 83.58 MB
Sending build context to Docker daemon
Step 0 : FROM scratch
Pulling repository scratch
511136ea3c5a: Pulling image (latest) from scratch, endpoint: https://registry-1.511136ea3c5a: Download complete
Status: Downloaded newer image for scratch:latest
---> 511136ea3c5a
Step 1 : MAINTAINER Keith Sharp <kms(a)passback.co.uk>
---> Running in 9091a442001f
---> bbcce511a8de
Removing intermediate container 9091a442001f
Step 2 : ADD Fedora-Docker-Base-20141029-21_Beta.x86_64.tar.gz /
---> 7058f928f119
Removing intermediate container de568a0cb7f8
Successfully built 7058f928f119
3) So far so good, the images show up as expected:
$ sudo docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
passback/fedora 21beta 7058f928f119 2 minutes ago 225.7 MB
scratch latest 511136ea3c5a 17 months ago 0 B
4) However, when I try to launch my new image I hit a problem:
$ sudo docker run --rm -ti passback/fedora:21beta /bin/sh
2014/11/26 14:15:10 Error response from daemon: Cannot start container 19fad5c0c8e1a11784b616d17d632c9a8978bdfed2fb2aca75252e28619ef5c1: exec: "/bin/sh": stat /bin/sh: no such file or directory
5) I had thought it was because I was missing a CMD or ENTRYPOINT instruction so I tried creating a new image based on this Dockerfile:
FROM passback/fedora:21beta
MAINTAINER Keith Sharp <kms(a)passback.co.uk>
CMD ["/bin/bash"]
6) The build works, but when I try to run I get the same error:
$ sudo docker run --rm -ti passback/test
2014/11/26 14:19:24 Error response from daemon: Cannot start container 1a20d7ceade9f4bc2d729ca081c10d849fe941e748de804fb1ad75abbf4d4941: exec: "/bin/bash": stat /bin/bash: no such file or directory
I'm sure I'm missing something simple, but no amount of searching is helping. Could someone point me in the right direction?
Thanks,
Keith.
9 years, 4 months
TC4 AMIs now available
by David Gay
TC4 x86_64 base and atomic AMIs are now available in all EC2 regions.
For those of you unaware, I've taken to adding AMI IDs for our purposes on the wiki, at https://fedoraproject.org/wiki/Cloud/Images. I figured it was a better place than my Fedora People page or personal website. Feel free to message me with any questions, comments, or concerns.
-- oddshocks
9 years, 4 months
Adding open-vm-tools package to Fedora Atomic
by Ravindra Kumar
Hi all,
I'm the maintainer for open-vm-tools package in Fedora.
For the benefit of Fedora Atomic users on VMware platform, I would like to add open-vm-tools package to Fedora Atomic.
Could somebody please advise/help me with the process involved to get open-vm-tools package in Fedora Atomic?
Thanks in advance,
Ravindra
9 years, 4 months
Better testimonial for site?
by Paul W. Frields
Right now the Cloud flavor page on the new website has a single
testimonial:
“Fedora Atomic Host is the most up-to-date way to deploy Docker
containers.” – Joe Brockmeier, Cloud Dude
AIUI there were one or more Cloud WG contributors trying to get us a
better testimonial. We've already shipped strings to translators but
we could put a better quote in place on Monday if someone actually
gets us the quote.
Can someone advise on status here?
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
9 years, 4 months