Hi cloud group,
based on [1], the working groups are expected to gather feedback from
users that should help defining next steps in Fedora.next development.
Since there are no direct users of Env Stacks group and it makes sense
to be able to segment the answers by audience, Env Stacks
Hi Adam & co.,
I think the container guidelines should include a section about the
Layered Images used as a base for other Layered Builds. I've created an
updated draft that also fixes label names to use the lower-case convention:
hhorak added a new comment to an issue you are following:
``
I'd like to take this, since we already have nicely working containers based on
CentOS and RHEL RPMs [1], so having a similar image based on Fedora image
(working fine in OpenShift) will be easy for us..
[1]
hhorak added a new comment to an issue you are following:
``
I'd like to take this, since we already have nicely working containers based on
CentOS and RHEL RPMs [1], so having a similar image based on Fedora image
(working fine in OpenShift) will be easy for us..
[1]
hhorak added a new comment to an issue you are following:
``
This is a good point, thanks for that. It think the guidelines don't cover the
case where we have FROM fedora:25 for image A and then FROM A for image B. In
my opinion this will be quite common case and we should have it covered in
hhorak added a new comment to an issue you are following:
``
Thanks for the quick turn-around, it looks like resolved now.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/248
___
cloud mailing list --
hhorak reported a new issue against the project: `atomic-wg` that you are
following:
``
One issue with the Fedora Containers Guidelines I've realized -- the 'help'
LABEL has different semantic in `atomic` tool than in the guidelines.
The description of the 'help' label in the container
hhorak added a new comment to an issue you are following:
``
Cool, but I don't think it helps here, since the real problem is not during
build time (how to get the help.1 file into the image), but during run time,
that help label is used for two different things now.
``
To reply, visit the
hhorak added a new comment to an issue you are following:
``
Example of multi-line description is here:
https://hhorak.fedorapeople.org/httpd-docker/Dockerfile
I think it works still quite well and looks better in the Dockerfile than one
long line IMO.
Anyway, the New requirements seem fine to
hhorak added a new comment to an issue you are following:
``
> ad 3: I expect that OSBS in Fedora uses atomic-reactor that is able to
> convert and add the README.md from dist-git to help.1 and add the COPY
> command into the Dockerfile. Why not use this feature? It would limit the
>
On 03/09/2017 05:40 PM, Adam Miller wrote:
On Thu, Feb 23, 2017 at 12:07 PM, Honza Horak <hho...@redhat.com> wrote:
Hi Adam & co.,
I think the container guidelines should include a section about the Layered
Images used as a base for other Layered Builds. I've created an updated
draft
hhorak reported a new issue against the project: `atomic-wg` that you are
following:
``
I think the container guidelines should include a section about the Layered
Images used as a base for other Layered Builds. I've created an updated
draft that also fixes label names to use the lower-case
hhorak added a new comment to an issue you are following:
``
For images like mariadb, I'd like to set the version to major version (e.g.
10.1), which is what users care (take a look how tags look like on docker hub).
Such major version is different than RPM version (e.g. 10.1.23) and also does
hhorak reported a new issue against the project: `atomic-wg` that you are
following:
``
I believe that setting the architecture label in every layered Dockerfile is
not necessary, it might be even problematic once we'll have containers on
non-intel platforms, because then we'd need to either
14 matches
Mail list logo
