Re: [atomic-devel] Consiering a host UID/GID upgrade discontinuity (breaking CentOS7 Atomic and F22)

[Matthew Miller <mattdm mattdm org>]

On Wed, May 06, 2015 at 03:47:57PM -0400, Colin Walters wrote:
> It was already decided that Atomic was non-blocking, though I don't
> have the reference to hand.

Specifically, it wasn't decided to be blocking, and non-blocking is the
default. :)

> The benefit is being able to seamlessly rebase between the
> CentOS/RHEL Atomic Host and Fedora.

That is really cool!


> What I'm arguing is it's far, far better to take this one time pain
> before deployment gets even larger.

Honestly, I think with Atomic at its current state, we might be able to
just document that upgrades aren't possible across these releases -
please take your containers and re-deploy 'em on a new host.


-- 
Matthew Miller            mattdm mattdm org             <http://mattdm.org/>
Fedora Project Leader  mattdm fedoraproject org  <http://fedoraproject.org/>