Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2023-03-02 from 15:00:00 to 16:00:00 UTC
At fedora-meeting-1(a)irc.libera.chat
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
Source: https://calendar.fedoraproject.org//meeting/1999/
Dear all,
You are kindly invited to the meeting:
Fedora Cloud Workgroup on 2023-02-16 from 15:00:00 to 16:00:00 UTC
At fedora-meeting-1(a)irc.libera.chat
The meeting will be about:
Standing meeting for the Fedora Cloud Workgroup
Source: https://calendar.fedoraproject.org//meeting/1999/
Hey there,
Nearly all of my Fedora usage is in the cloud (I guess I picked the right SIG to join) and one of my frustrations is finding the right image to use. 🥵
Fedora does make this fairly simple on the cloud page[0], but I see two issues here:
1) Sometimes new images are available in AWS, but the Fedora page points to an older version.
2) Sometimes I want an older version of Fedora (or rawhide!) and that's not listed.
When I want a particular version of Fedora in a container, it's really easy to fire up podman and pull some images from known URLs:
quay.io/fedora/fedora:rawhide
quay.io/fedora/fedora:37
quay.io/fedora/fedora:36
I'd love to have some kind of tool that would look up this information and give me the appropriate AMI ID at AWS so I could say "launch Fedora 37 latest" and get it where I want it. Frankly, I'd love this for CentOS, RHEL, and other distros, too. 💙
My team at Red Hat came up with the idea of a locator service that would gather data from upstream locations (AWS, Azure, GCP, and others), compile the image data into a common schema, and make it available for API calls and a web frontend.
CoreOS already does something like this and offers a JSON[1] file with a standardized schema that makes it easier to find the current released in various locations.
Would this type of application be useful for others in the Fedora community? We'd like to know if there would be broader interest here in this idea or if there's something else that makes more sense to pursue.
Thanks! 👋
[0] https://alt.fedoraproject.org/en/cloud/
[1] https://builds.coreos.fedoraproject.org/streams/stable.json
--
Major Hayden
Reproducer:
1. Build following containerfile:
FROM registry.fedoraproject.org/fedora:38
RUN dnf install -y systemd
ENTRYPOINT ["/sbin/init"]
STOPSIGNAL SIGRTMIN+3
$ podman build --tag "systemd:latest" .
2. Run container
$ podman run --detach -i --name test systemd
$ podman ps --all
CONTAINER ID IMAGE COMMAND CREATED
STATUS PORTS NAMES
5160fb46b6e2 localhost/systemd:latest 5 seconds ago
Exited (255) 5 seconds ago test
The container immediately terminates with exit status 255. The same
works (= container is up and running) with fedora:37 image.
We have daily builds of containers with systemd running and the last
time 38/rawhide container worked was January 25.
Thanks,
Pavel.