Re: [atomic-devel] Fedora Container Release

2018-03-23 Thread Clement Verna
> The Fedora version names crept in there as a result of a > miscommunication, I think. I expected us to use tags or other metadata > for the base Fedora version. I don't think we really want that in the > path. Thanks for the input and the feedback. I will look at what we can do to remove the Fe

Re: [atomic-devel] Fedora Container Release

2018-03-22 Thread Matthew Miller
On Thu, Mar 22, 2018 at 10:44:05AM -0400, Stephen Milner wrote: > > The Fedora version names crept in there as a result of a > > miscommunication, I think. I expected us to use tags or other metadata > > for the base Fedora version. I don't think we really want that in the > > path. > Ah, that make

Re: [atomic-devel] Fedora Container Release

2018-03-22 Thread Stephen Milner
On Thu, Mar 22, 2018 at 10:20 AM, Matthew Miller wrote: > On Tue, Mar 20, 2018 at 10:24:06AM +0100, Clement Verna wrote: >> I also feel that having to specify the version fedora during the pull >> is not a very nice user experience. (ie docker pull >> registry.fedoraproject.org/f27/nginx) >> Somet

Re: [atomic-devel] Fedora Container Release

2018-03-22 Thread Matthew Miller
On Tue, Mar 20, 2018 at 10:24:06AM +0100, Clement Verna wrote: > I also feel that having to specify the version fedora during the pull > is not a very nice user experience. (ie docker pull > registry.fedoraproject.org/f27/nginx) > Something more user friendly would be docker pull > registry.fedorap

Re: [atomic-devel] Fedora Container Release

2018-03-20 Thread Stephen Milner
On Mar 20, 2018 5:24 AM, "Clement Verna" wrote: Thanks all for the feedbacks, I am 100% behind the idea that, the end user does not care about which fedora base image is used (as long as he trust that patch and security fixes are applied). If I want to use the nginx container for example as a us

Re: [atomic-devel] Fedora Container Release

2018-03-20 Thread Clement Verna
Thanks all for the feedbacks, I am 100% behind the idea that, the end user does not care about which fedora base image is used (as long as he trust that patch and security fixes are applied). If I want to use the nginx container for example as a user I am more interested in the version of nginx th

Re: [atomic-devel] Fedora Container Release

2018-03-19 Thread Dusty Mabe
On 03/19/2018 04:30 PM, Colin Walters wrote: > > > On Mon, Mar 19, 2018, at 3:38 PM, Clement Verna wrote: > >> So if you maintain a container could you please build your container >> against the f28 and master branch. Everyone please keep in mind that Clement is a new team member and is inher

Re: [atomic-devel] Fedora Container Release

2018-03-19 Thread Stephen Milner
Thanks for the note Clement. Inline... On Mar 19, 2018 4:31 PM, "Colin Walters" wrote: On Mon, Mar 19, 2018, at 3:38 PM, Clement Verna wrote: > So if you maintain a container could you please build your container > against the f28 and master branch. There's a fairly important deeper question

Re: [atomic-devel] Fedora Container Release

2018-03-19 Thread Colin Walters
On Mon, Mar 19, 2018, at 3:38 PM, Clement Verna wrote: > So if you maintain a container could you please build your container > against the f28 and master branch. There's a fairly important deeper question here: Do we really want to build all of these containers against each fedora release? Do

[atomic-devel] Fedora Container Release

2018-03-19 Thread Clement Verna
Hi all, I am currently working on getting the Fedora Container release to have a predictable 2 weeks cycle. With the Fedora engineering team we have been able to release containers for f26 and f27 last Thursday(15 March 2018). We would also like to release containers for f28 and rawhide, but to