On 07/13/2016 10:26 PM, Dusty Mabe wrote: > > > On 07/13/2016 10:19 PM, Dusty Mabe wrote: >> >> >> On 07/13/2016 09:47 PM, Adam Miller wrote: >>> Hello all, >>> On behalf of many various groups within the Fedora Project >>> including the Release Engineering and Tooling teams, Websites Team, >>> and Cloud Working Group I would like to announce the Fedora Atomic >>> Host Two Week Release now based on Fedora 24 and powered by an all new >>> Compose process and tooling, brand new AutoCloud, updates to the >>> website code, as well as updates to the release tool. >>> >>> At this time the Fedora Atomic Host images are immediately available here: >>> >>> https://getfedora.org/en/cloud/download/atomic.html >>> >>> Checksums here: >>> http://alt.fedoraproject.org/pub/alt/atomic/stable/CloudImages/x86_64/images/Fedora-CloudImages-24-20160712.0-x86_64-CHECKSUM >>> http://alt.fedoraproject.org/pub/alt/atomic/stable/Atomic/x86_64/iso/Fedora-Atomic-24-20160712.0-x86_64-CHECKSUM >>> >>> We collectively apologize for the lag time since the last Two Week >>> release, we realize it has been far longer than Two Weeks. That was >>> unfortunately the side effect of so many components within the process >>> to produce the images being retooled and then a break down in >>> coordination of some of cross-team pieces. >>> >>> On behalf of everyone involved, my apologies to everyone who has been >>> impacted by the delay and we will continue to strive to do better in >>> the future. >>> >>> Thank you, >>> -AdamM >> >> Thank you so much Adam! You have been amazing. >> >> A new entry for the `fedora/24-atomic-host` vagrant box has been made in Atlas: >> >> https://atlas.hashicorp.com/fedora/boxes/ >> https://atlas.hashicorp.com/fedora/boxes/24-atomic-host >> >> This version is at: >> https://atlas.hashicorp.com/fedora/boxes/24-atomic-host/versions/20160712 >> >> To try it out: >> >> vagrant init fedora/24-atomic-host; vagrant up >> > > As a side note - the vagrant boxes do have a bug in them where it > tries to do the default rsync to /vagrant/, which fails because it is > an atomic host and the /vagrant/ directory can't be created. > > I filed a bug for this a while back and dgilmore was looking at it but > I don't know what progress he made. > > The workaround for now is to override that rsync in the vagrantfile > with something like: > > config.vm.synced_folder "./", "/vagrant", disabled: 'true' doh.. link is here: https://pagure.io/pungi-fedora/issue/26 _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
