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 maintain more copies of Dockerfiles with different architecture labels or remove it later (when we'll have more layered Dockerfiles to maintain at that point).
So, I'd like to propose to set the architecture label in the container base image, so it is inherited in the layered images and we don't need to hard-code it there. Then, setting architecture label should be made prohibited (or obsolete) in https://fedoraproject.org/wiki/Container:Guidelines. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/276
The issue: `Set architecture label in the base container image` of project: `atomic-wg` has been assigned to `maxamillion` by maxamillion.
maxamillion added a new comment to an issue you are following: `` Do you want this to be a LABEL or an ENV? ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/276
dustymabe added a new comment to an issue you are following: `` Discussed in the atomic working group meeting today. The proposal in the description sounds reasonable. Assuming we need to set an architecture label, then making layered images inherit from the base image makes sense. This assumes that there is not some technical reason why this can't be achieved.
+1 ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/276
maxamillion added a new comment to an issue you are following: `` PR Submitted to imagefactory to add this functionality. https://github.com/redhat-imaging/imagefactory/pull/402
Once merged, we'll get the configurations in place with [pungi-fedora](https://pagure.io/pungi-fedora) ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/276