jberkus reported a new issue against the project: `atomic-wg` that you are following:
``
A "minimal" build of the base container image exists, but isn't official or generally available from the repository. We need this minimal image for a few reasons:
* users care about container size from some use-cases (think super-micro-services and serverless)
* arguably a more minimal container is easier to secure
* other linux distros offer some kind of small base image
* buildah, now in alpha, *really* benefits from a minimal base image
For this to succeed, we'd want the following base images as part of registry.fedoraproject.org:
* fedora-minimal:25
* fedora-minimal:26
* fedora-minima:latest
Given that the minimal image will differ less per release version (since it has less plubming), it would be perfectly acceptable to have a very short expiration window on older release versions, or only supporting the current Fedora release.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/290
jberkus reported a new issue against the project: `atomic-wg` that you are following:
``
I pave my bare metal cluster using a kickstart similar to the one here: http://www.projectatomic.io/blog/2016/10/install-with-kickstart/
However, as of f26 release, this no longer works. Which is surprising given that f26 alpha did work. The problem is this line in my updated kickstart:
ostreesetup --osname="fedora-atomic" --remote="fedora-atomic" --url="file:////run/install/repo/content/repo" --ref="fedora/26/x86_64/atomic-host" --nogpg
This should pull the ref from the local media (USB key). However, what I get now is "openat: no such file or directory" So somehow the ref is broken in the ISO.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/296
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
Let's collect ideas for talk/workshop proposals at [Flock](https://flocktofedora.org/)
Due date for CFP submissions is June 15th
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/279
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2017-07-12 from 17:00:00 to 18:00:00 UTC
At fedora-meeting-1(a)irc.freenode.net
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
Source: https://apps.fedoraproject.org/calendar/meeting/1999/
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
This ticket will be used throughout the f26 release to track potential blocker bugs and/or important bugs for the next release. A blocker bug is a bug that we will choose not to release on if it is not fixed. An important bug is a bug that we want fixed but may choose not to block on.
**Blocker Bugs**
-
**Important Bugs**
- none
Over time only the description of this bug will be edited for updates. Please do not add comments to this issue.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/261
bowlofeggs reported a new issue against the project: `atomic-wg` that you are following:
``
I had a weird bug today where my Dockerfile in my master branch had a FROM line that specified Fedora 26, which caused the container to be built into Fedora 26 tags instead of Rawhide. It was obviously my mistake, but it occurred to me that it might be nice if the build system used my branch to determine which FROM line to use if my Dockerfile doesn't define one, so that it works a little more similarly to RPMs when I do a fedpkg container-build. Since some containers don't base off the base image, it would be important that this only happen when FROM is missing, but it could be nice for containers that do want the base image.
Another idea: If the from line doesn't contain a tag (after a :, like ```:f26```), the tag could be appended. This might work for containers that don't use the base image?
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/293