dustymabe added a new comment to an issue you are following:
``
i would say we have a pre-release page and then switch the website over on "F26
big release" day
The pre-release page for f26 atomic could just get updated once a day to list
the latest nightly image that was built. WDYT?
``
To
Can a couple of people give the following atomic image a spin and verify
cloud-init works for them?
https://www.dropbox.com/s/4xp2pie70h1jf7y/cloud-init-testing-atomic.qcow2?dl=0
Please report success/failure in:
https://bodhi.fedoraproject.org/updates/FEDORA-2017-1f675fd070
Thanks,
Dusty
On 01/30/2017 03:25 PM, p...@wesleytech.com wrote:
> Greetings! Can someone please explain the process for publishing Fedora AMI's
> to AWS?
We use fedimg to upload images to AWS. As far as I know it hasn't been
touched in a while and needs some love:
https://github.com/fedora-infra/fedimg
>
On 01/30/2017 04:00 PM, Thomas Mueller wrote:
> Hi
>
> Wasn't the fedora/25-cloud-base updated too?
>
> https://atlas.hashicorp.com/fedora/boxes/25-cloud-base lists v20161122
> (last release 2 months ago).
Hi Thomas,
Unfortunately we only officially "release" the Atomic images every two
We are going to try to release our next 2WA release this week.
Feel free to test out today's build and see if there are any issues!
The atomic images are here:
https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170131.0/compose/CloudImages/x86_64/images/
The ISO image is
dustymabe added a new comment to an issue you are following:
``
closing since bex requested it.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/165
___
cloud mailing list -- cloud@lists.fedoraproject.org
Hey team,
Right now some very critical pieces of Atomic Host have packages
that are in testing. It would be great if we can get some people
to take the updates-testing tree for a spin and report any issues.
Here is a summary of what is in updates-testing vs what is in updates:
Changed:
On 02/08/2017 05:42 AM, James Hogarth wrote:
> Hi guys,
>
> I just submitted a container review request for owncloud.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1420275
>
> Since PHP is stuck at 5.4 in EL7 this is my first step of still being
> able to provide owncloud to EL7 users when
dustymabe added a new comment to an issue you are following:
``
+1 for current name space
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/202
___
cloud mailing list -- cloud@lists.fedoraproject.org
To
On 02/08/2017 04:35 PM, Adam Williamson wrote:
> On Tue, 2016-12-06 at 16:38 -0500, Matthew Miller wrote:
>> I think we had general agreement around what we want to do here:
>> have the Cloud Base Image become instead Fedora Server, but shipped
>> as a cloud image and made available in cloud
After some discussions with mattdm and sgallagh about the cloud base
image and the server WG we have decided for now to leave the cloud
base image out of the server WG. Obviously it doesn't make sense to
have it stay as owned by the Atomic WG so here is what I would like to
propose:
- Have the
dustymabe added a new comment to an issue you are following:
``
-1 on docker 1.13 for now: https://twitter.com/jbeda/status/826969113801093121
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/196
___
cloud
On 02/02/2017 10:56 AM, nore...@fedoraproject.org wrote:
>
> A new update of Fedora Cloud Atomic Host has been released and can be
> downloaded at:
>
> Images can be found here:
>
> https://getfedora.org/en/cloud/download/atomic.html
>
> Respective signed CHECKSUM files can be found
dustymabe added a new comment to an issue you are following:
``
Closing this as it no longer seems to be an issue:
```
[vagrant@f25vanilla ~]$ rpm -qa | grep uboot
[vagrant@f25vanilla ~]$ rpm -qa | grep dtc
[vagrant@f25vanilla ~]$ cat /etc/os-release
NAME=Fedora
VERSION="25 (Cloud Edition)"
The status of the issue: `Remove uboot-tools from cloud base package set` of
project: `atomic-wg` has been updated to: Closed as Fixed by dustymabe.
https://pagure.io/atomic-wg/issue/32
___
cloud mailing list -- cloud@lists.fedoraproject.org
To
dustymabe added a new comment to an issue you are following:
``
I think we should close this issue unless there are any outstanding issues.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/154
___
cloud
The status of the issue: `Fedora Cloud Base Vagrant Boxes Don't Allow Vagrant
User To su To Other Users` of project: `atomic-wg` has been updated to: Closed
as Fixed by dustymabe.
https://pagure.io/atomic-wg/issue/173
___
cloud mailing list --
dustymabe added a new comment to an issue you are following:
``
confirmed - the patch works. For the record I tested on the following image:
dustymabe added a new comment to an issue you are following:
``
we should close this ticket - we should do what makes sense and stop bogging
ourselves down with "process"
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/171
On 02/03/2017 09:19 AM, Thomas Mueller wrote:
>
>
> Am 03.02.2017 um 14:41 schrieb Matthew Miller:
>> On Fri, Feb 03, 2017 at 09:43:47AM +0100, Thomas Mueller wrote:
>>> Also download numbers on atlas indicate more interest for cloud-base
>>> than atomic for vagrant.
>> Part of that might be
dustymabe added a new comment to an issue you are following:
``
trishnag, currently still the same - it won't matter if we fix it now because
we have not been releasing cloud base images so even if we fix it it would not
get released for the cloud base image until f26. That is unless we decide
We had a brief meeting with just open floor today since a lot of people
are still traveling.
summary:
https://meetbot.fedoraproject.org/fedora-meeting-1/2017-02-01/fedora_atomic_wg.2017-02-01-17.02.html
full log:
On 01/21/2017 02:25 PM, Vasiliy Tolstov wrote:
> By in case of ostree I mean rpm-ostree install. Or rpm-ostree does not use
> dnf at all?
>
It doesn't use dnf at all. AFAIU rpm-ostree had code to install rpms
for a while and then that code was broken out and eventually made into
microdnf. So
On 01/21/2017 07:41 AM, Vasiliy Tolstov wrote:
> 2017-01-21 7:22 GMT+03:00 Dusty Mabe <du...@dustymabe.com>:
>> https://pagure.io/fedora-kickstarts/pull-request/120
>>
>> This is an attempt at making a more lightweight container image.
>> Using microdnf [
On 01/20/2017 04:51 PM, Dusty Mabe wrote:
>
> Note: please don't respond to this email. Please continue discussion
> in the linked ticket.
>
> This is a partial implementation of releng ticket 6545 [1] which is a
> migration of the old releng trac ticket 63
On 01/22/2017 07:33 PM, Philip Rhoades wrote:
> People,
>
> I have a F25 64bit server - it is mainly used to run Qmail and EZMLM but
> also has a couple of trivial web sites on it. I am thinking of moving
> about a dozen small Rails and Jekyll websites off Digital Ocean and back
> on to
New build just finished with new kernel and new kubernetes versions that
prevented us from releasing our 2wk release last week.
The vm images are here:
https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170124.1/compose/CloudImages/x86_64/images/
The iso is here:
Dennis asked me to file a change for a container minimal image that I proposed
to the Fedora kickstarts repo[1]. Here [2] is a link to the change wiki page.
If I did anything wrong please be gentle, this is my first one.
Dusty
[1] - https://pagure.io/fedora-kickstarts/pull-request/120
[2] -
On 01/27/2017 12:49 PM, Garrett Holmstrom wrote:
> On 2017-01-25 07:02, Dusty Mabe wrote:
>> This patch set backports a patch from upstream to delete a systemd
>> dep loop. It also disables tests that try to contact the internet.
>
> The unit tests use mock data; the is
picked from commit 9785285
---
Delete-GCE-test-it-s-failing.patch | 182 +
cloud-init.spec| 3 +
2 files changed, 185 insertions(+)
create mode 100644 Delete-GCE-test-it-s-failing.patch
diff --git a/Delete-GCE-test-it-s-failing.patch
This patch set backports a patch from upstream to delete a systemd
dep loop. It also disables tests that try to contact the internet.
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to
backported from the following upstream commit:
https://git.launchpad.net/cloud-init/commit/?id=3705bb5964a2ff3f9a67265e6d090a112b35e40c
fixes the following bz:
https://bugzilla.redhat.com/show_bug.cgi?id=1393094
---
cloud-init-0.7.8-systemd-loop.target | 37
On 01/25/2017 04:28 AM, nore...@fedoraproject.org wrote:
>
> A new update of Fedora Cloud Atomic Host has been released and can be
> downloaded at:
>
> Images can be found here:
>
> https://getfedora.org/en/cloud/download/atomic.html
>
> Respective signed CHECKSUM files can be found
On 01/25/2017 04:28 AM, nore...@fedoraproject.org wrote:
>
> A new update of Fedora Cloud Atomic Host has been released and can be
> downloaded at:
>
> Images can be found here:
>
> https://getfedora.org/en/cloud/download/atomic.html
>
> Respective signed CHECKSUM files can be found
I'm in Brno this week for devconf and won't make the meeting today. Please grab
me on irc or send me an email if you need something.
Dusty
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email to
https://pagure.io/fedora-kickstarts/pull-request/120
This is an attempt at making a more lightweight container image.
Using microdnf [1] i'm able to get the image down to about 110M,
but I'm hoping to get it under 100M soon.
You can give this image a shot by pulling "dustymabe/fedora-min".
You
Note: please don't respond to this email. Please continue discussion
in the linked ticket.
This is a partial implementation of releng ticket 6545 [1] which is a
migration of the old releng trac ticket 6313 [2].
Gross simplification: In the ticket two things were requested:
- The ostree
On 01/15/2017 04:03 PM, Dusty Mabe wrote:
>
> I noticed today when comparing two trees, one from Dec25 and the
> latest one, that the version of cockpit went backwards.
>
> !cockpit-bridge-126-1.fc25.x86_64
> =cockpit-bridge-120-1.fc25.x86_64
> !cockpit-docker-126-1.f
On 01/17/2017 11:26 AM, Stef Walter wrote:
>
> Indeed. We'll be releasing Cockpit 129 shortly, which will include an
> Obsoletes directive in the RPM and should fix this issue. Sorry for the
> breakage.
No worries. Glad I saw it and we plan on detecting this sort of thing
in the future.
Dusty
hey all,
I am about to head to the airport. I'm hoping to make the meeting from
the airport, fingers crossed.
I added a few items to the meeting tag that I'd like the WG to
discuss.
- clarify policy on atomic host support for older Fedora "number" releases
dustymabe reported a new issue against the project: `atomic-wg` that you are
following:
``
We are now *releasing* OSTree content every two weeks rather than every night
([link](http://www.projectatomic.io/blog/2017/02/matching-fedora-ostree-released-content-with-each-2week-atomic-release/)).
dustymabe added a new comment to an issue you are following:
``
> @jbrooks
> I'd just like to clarify for anyone reading this that "rolling" doesn't mean
> rolling like rawhide or suse tumbleweed, unless the wheel you have in mind is
> giant and square and "turns" once each six months when a
dustymabe added a new comment to an issue you are following:
``
> -1 on dropping Life Support for N-1 unless we're ready to shift to rolling
> releases. That's pretty much the worst of all possible worlds.
> Proposed policy: Life Support+
> From the date N is released:
>
> We continue offering
dustymabe reported a new issue against the project: `atomic-wg` that you are
following:
``
Now that ostree metadata is signed we should start configuring our media so
that the resulting systems verify signatures with something like this:
```
# cat /etc/ostree/remotes.d/fedora-atomic.conf
dustymabe added a new comment to an issue you are following:
``
It would be great if this bug got resolved before we enabled this:
https://github.com/projectatomic/rpm-ostree/issues/630
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/230
dustymabe commented on the pull-request: `manifest: Change the ref/branch name
to be fedora/.../atomic-host` that you are following:
``
we didn't really talk about replacing `fedora-atomic` with `fedora`. I think
I'm +1 though. I'll notify the ticket what we are changing it to for f26 and
On 02/16/2017 12:49 PM, nore...@fedoraproject.org wrote:
>
> A new Fedora Atomic Host update is available via an OSTree commit:
>
> Commit: 5a9de04163a60c5f2771b3d307601fa4e2234f12b662c97e28290b7bcbdb43f0
> Version: 25.59
>
>
> Existing systems can be upgraded in place via e.g. `atomic host
On 02/16/2017 08:51 AM, Josh Boyer wrote:
> On Wed, Feb 15, 2017 at 10:45 AM, Dusty Mabe <du...@dustymabe.com> wrote:
>>
>>
>> On 02/08/2017 08:01 PM, Dusty Mabe wrote:
>>>
>>> After some discussions with mattdm and sgallagh about the cloud bas
On 02/17/2017 02:42 AM, Thomas Mueller wrote:
>
>
> Am 16.02.2017 um 14:51 schrieb Josh Boyer:
>> On Wed, Feb 15, 2017 at 10:45 AM, Dusty Mabe <du...@dustymabe.com> wrote:
>>>
>>> On 02/08/2017 08:01 PM, Dusty Mabe wrote:
>>>> After some d
dustymabe added a new comment to an issue you are following:
``
So we had a working session on Wednesday and changed the etherpad quite a bit.
Are we pretty much done with it now? Can we give it a final pass and then a
"ok" for moving it to the Wiki?
``
To reply, visit the link below or just
dustymabe added a new comment to an issue you are following:
``
@jberkus - i'm fully operating in many contexts. I'm thinking about many
different use cases where systems are upgraded manually and where systems are
upgraded automatically. What I would like to do is operate on a principle of
dustymabe added a new comment to an issue you are following:
``
Another alternative is that we shorten this by just including a shortcommit of
the ostree commit id in the image name:
```
Fedora-Atomic-25-20170215.1.aabbccdd.x86_64.qcow2
```
The negative is that OSTree version numbers are less
dustymabe added a new comment to an issue you are following:
``
>
> That said I think we're going to run into pungi issues here.
Yes. This is modeled from the compose id, which takes the form of
`Fedora-Atomic-25-20170215.1` with the date embedded in there. I think they did
this for good
dustymabe added a new comment to an issue you are following:
``
> +1 for atomic-host.
> How do we inform the users? Can we provide some kind of link to the old name
> so that we don't break everything?
I think if we don't plan to keep the old name around forever then we should
just go ahead
dustymabe added a new comment to an issue you are following:
``
ok so let me flesh this out just a little more. Current proposal is something
like `25.20170130.0` just for the OSTree *version* that is part of the ostree
repo; i.e. the version you see when you run `rpm-ostree status`. Now we
dustymabe added a new comment to an issue you are following:
``
> I'm not sure I understand. If you want a new unified repo to be brand new,
> that's fine w/ me. I just want to get rid of the separate refs for each major
> version / required rebase nonsense.
>
I'm just saying that I don't
On 02/24/2017 12:22 PM, Jonathan Lebon wrote:
>> - pre-loading containers on system startup
>> * there is a need for being able to load containers on system
>> startup into the container runtime. I think jlebon already
>> worked on something like this maybe. Either way the idea
dustymabe added a new comment to an issue you are following:
``
note is added to the repo and we have started converting popular ones to go
through the fedora container review process. closing this
``
To reply, visit the link below or just reply to this email
dustymabe added a new comment to an issue you are following:
``
roshi wanted to take a look at this. removing from meeting agenda for now
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/169
___
cloud
dustymabe added a new comment to an issue you are following:
``
yes. more than once a day is a possibility that is why I added the number to
the end: `20170130.0`, `20170130.1`
So I think we are settling in on `year.month.day.serial` where serial is the
increment for the number of the ostrees
Sayan, can you take a look at this?
On 02/21/2017 04:44 PM, Stephen John Smoogen wrote:
> There is an outstanding bug report
> https://bugzilla.redhat.com/show_bug.cgi?id=1423753 that came up in
> the Fedora Server meeting today.
>
> Does someone know who can make this fixed? And who owns the
dustymabe added a new comment to an issue you are following:
``
in that model I don't think adding *just* the year and/or yearsuffix gives us
that much added value in Fedora (because of the short lifespan of a Fedora
number release). I think if we have the date we should have a full
On 02/14/2017 10:45 AM, Josh Berkus wrote:
> On 02/14/2017 06:33 AM, Dusty Mabe wrote:
>>
>>
>> On 02/13/2017 10:42 PM, Josh Berkus wrote:
>>> On 02/13/2017 07:32 AM, Dusty Mabe wrote:
>>>> We are going to try to release our next 2WA release this week
On 02/09/2017 10:16 AM, Dusty Mabe wrote:
>
>
> On 02/09/2017 10:05 AM, Dusty Mabe wrote:
>>
>> We have been using https://dl.fedoraproject.org/pub/fedora/linux/atomic/25/
>> for the
>> remote for atomic host for some time. This is actu
On 02/13/2017 12:11 PM, Thomas Mueller wrote:
>
>
> Am 13.02.2017 um 16:32 schrieb Dusty Mabe:
>> We are going to try to release our next 2WA release this week.
>> Feel free to test out today's build and see if there are any issues!
>>
>> The at
On 02/14/2017 02:28 AM, Thomas Mueller wrote:
>
>
> Am 13.02.2017 um 22:43 schrieb Dusty Mabe:
>>
>> On 02/13/2017 12:11 PM, Thomas Mueller wrote:
>>>
>>> Am 13.02.2017 um 16:32 schrieb Dusty Mabe:
>>>> We are going to try to release our nex
On 02/13/2017 10:42 PM, Josh Berkus wrote:
> On 02/13/2017 07:32 AM, Dusty Mabe wrote:
>> We are going to try to release our next 2WA release this week.
>> Feel free to test out today's build and see if there are any issues!
>>
>> The atomic i
We are going to try to release our next 2WA release this week.
Feel free to test out today's build and see if there are any issues!
The atomic images are here:
https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170213.0/compose/CloudImages/x86_64/images/
The ISO image is
We just released a blog post about changing the way we release OSTree
content to the public:
http://www.projectatomic.io/blog/2017/02/matching-fedora-ostree-released-content-with-each-2week-atomic-release/
Here is the TL;DR version:
The default Fedora cadence for updates in the RPM streams
On 02/09/2017 10:05 AM, Dusty Mabe wrote:
>
> We have been using https://dl.fedoraproject.org/pub/fedora/linux/atomic/25/
> for the
> remote for atomic host for some time. This is actually just a redirect to
> https://kojipkgs.fedoraproject.org/atomic/25/. Since we have been u
On 02/16/2017 12:49 PM, nore...@fedoraproject.org wrote:
>
> A new Fedora Atomic Host update is available via an OSTree commit:
>
> Commit: 5a9de04163a60c5f2771b3d307601fa4e2234f12b662c97e28290b7bcbdb43f0
> Version: 25.59
>
>
> Existing systems can be upgraded in place via e.g. `atomic host
dustymabe reported a new issue against the project: `atomic-wg` that you are
following:
``
After talking with people from the fedora community and from the atomic WG it
has become clear that there is a lot of confusion on our policy for support for
N-1 releases of Fedora Atomic Host.
First
dustymabe added a new comment to an issue you are following:
``
+1 to rebuilding containers regularly - we may have to revisit this as the
number of containers we support increases.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/200
dustymabe added a new comment to an issue you are following:
``
seems like enough people are +1. Closing this "question".
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/202
___
cloud mailing list --
The status of the issue: `ISO missing embedded content` of project: `atomic-wg`
has been updated to: Closed as Invalid by dustymabe.
https://pagure.io/atomic-wg/issue/227
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an
On 02/08/2017 08:01 PM, Dusty Mabe wrote:
>
> After some discussions with mattdm and sgallagh about the cloud base
> image and the server WG we have decided for now to leave the cloud
> base image out of the server WG. Obviously it doesn't make sense to
> have it stay as owned b
The previous candidate had an issue with the ISO that we wanted to resolve.
We are going to run these new images through testing and try to release today
unless we get any negative feedback. Here is the new candidate:
The atomic images are here:
dustymabe added a new comment to an issue you are following:
``
> We are making docker-storage-setup more generic (to be usable by other
> container runtime as well, apart from docker). So in an attempt to do that,
> we are introducing new options.
> EXTRA_VOLUME_NAME="docker-root-lv"
>
dustymabe added a new comment to an issue you are following:
``
> We are making docker-storage-setup more generic (to be usable by other
> container runtime as well, apart from docker). So in an attempt to do that,
> we are introducing new options.
> EXTRA_VOLUME_NAME="docker-root-lv"
>
dustymabe added a new comment to an issue you are following:
``
> vgoyal
> Thinking more about it. I think EXTRA_VOLUME_NAME is more intuitive. Reason
> being that this script sets up thin pool volume as well and that's a
> container volume too. EXTRA sort of makes it explicit
that this volume
dustymabe added a new comment to an issue you are following:
``
> vgoyal
> Thinking more about it. I think EXTRA_VOLUME_NAME is more intuitive. Reason
> being that this script sets up thin pool volume as well and that's a
> container volume too. EXTRA sort of makes it explicit
that this volume
On 01/17/2017 11:29 AM, Jason Brooks wrote:
>
> I looks good to me, I say we get rolling with it and iterate as
> needed, but the basic plan here seems solid.
>
+1
___
cloud mailing list -- cloud@lists.fedoraproject.org
To unsubscribe send an email
On 01/13/2017 11:18 AM, Antonio Murdaca wrote:
>
>
>
> That sounds good. However, I didn't fully understand how to achieve that. Do
> you mean that docker-latest shouldn't build docker-latest anymore but just
> require "docker" and make a symlink out of it?
Exactly. in other words, it's
I noticed today when comparing two trees, one from Dec25 and the
latest one, that the version of cockpit went backwards.
!cockpit-bridge-126-1.fc25.x86_64
=cockpit-bridge-120-1.fc25.x86_64
!cockpit-docker-126-1.fc25.x86_64
=cockpit-docker-120-1.fc25.x86_64
dustymabe reported a new issue against the project: `atomic-wg` that you are
following:
``
We should be sanity checking the content that goes into each new ostree update
of F25 atomic host. Here are some ideas:
- raise flag if any rpm go down in version/release
- raise flag if any rpm gets
There are a few bugs that are blocking 2wk release.
- one with the kernel that causes kube dns to not work
* https://bugzilla.redhat.com/show_bug.cgi?id=1414068
- one with kube that causes selinux breakage
* https://bugzilla.redhat.com/show_bug.cgi?id=1414096
We need to get these
On 01/17/2017 02:26 PM, Eric Paris wrote:
> On Tue, 2017-01-17 at 13:42 -0500, Dusty Mabe wrote:
>> There are a few bugs that are blocking 2wk release.
>>
>> - one with the kernel that causes kube dns to not work
>> * https://bugzilla.redhat.com/show_bug.cgi?id
On 01/15/2017 04:47 PM, Antonio Murdaca wrote:
>
>
> On Jan 15, 2017 10:07 PM, "Dusty Mabe" <du...@dustymabe.com
> <mailto:du...@dustymabe.com>> wrote:
>
>
>
> On 01/13/2017 11:18 AM, Antonio Murdaca wrote:
> >
> >
On 01/17/2017 01:42 PM, Dusty Mabe wrote:
> There are a few bugs that are blocking 2wk release.
>
> - one with the kernel that causes kube dns to not work
> * https://bugzilla.redhat.com/show_bug.cgi?id=1414068
> - one with kube that causes selinux breakag
dustymabe added a new comment to an issue you are following:
``
First build is out that contains this fix. Please test:
https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-25-20170118.1/compose/Atomic/x86_64/iso/
Keep in mind you will need to have a /boot partition in order for this
On 01/18/2017 12:57 PM, Michael Scherer wrote:
> Hi,
>
> so as people asked me on irc, it seems there was a lack of communication
> regarding the hardware for the FOSP project
> (https://pagure.io/atomic-wg/issue/153).
>
> Due to internal changes (on top of regular changes) on the other side
dustymabe added a new comment to an issue you are following:
``
> VM install of Fedora-Atomic-ostree-x86_64-25-20170118.1.iso to a clean LV
> succeeds, for both BIOS and UEFI firmware. Using default partitioning, the
> required layout is created. Both installations completely startup, I can
>
dustymabe added a new comment to an issue you are following:
``
OK I think we will settle on having an extra partition that is used as the root
store for `/var/lib/docker` on Atomic Host (i.e. we will have
`DOCKER_ROOT_VOLUME=yes` be the default) along with default to overlay2. We may
revisit
dustymabe reported a new issue against the project: `atomic-wg` that you are
following:
``
In the meeting today @runcom brought up the topic of:
- removing docker-latest in Fedora (mail thread on that
dustymabe added a new comment to an issue you are following:
``
> I think we should get docker-1.13 into Rawhide right away.
agree on this point. The discussion was meant to target f25.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/196
dustymabe added a new comment to an issue you are following:
``
> This should be easy to do with anaconda-based installs, but how would this
> work with images?
docker-storage-setup can do this for us. The images are only baked with an
`atomicos` VG and an `atomicos/root` LV.
dustymabe added a new comment to an issue you are following:
``
>
> This should be easy to do with anaconda-based installs, but how would this
> work with images?
>
> docker-storage-setup can do this for us. The images are only baked with an
> atomicos VG and an atomicos/root LV.
dustymabe added a new comment to an issue you are following:
``
> CONTAINER_LV_NAME
> CONTAINER_LV_MOUNT_PATH
That is better but I still think it's worth adding the "root" in there so that
the user knows this is where the container runtime's root will be mounted vs
the backend storage for
dustymabe added a new comment to an issue you are following:
``
> CONTAINER_LV_NAME
> CONTAINER_LV_MOUNT_PATH
That is better but I still think it's worth adding the "root" in there so that
the user knows this is where the container runtime's root will be mounted vs
the backend storage for
dustymabe added a new comment to an issue you are following:
``
Closing this as the fix is in and will be in the next two week release.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/185
___
cloud
201 - 300 of 875 matches
Mail list logo
