Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rockylinux:9 image missing /sbin/init or /usr/sbin/init #39

Closed
hwdsl2 opened this issue Dec 29, 2022 · 1 comment
Closed

rockylinux:9 image missing /sbin/init or /usr/sbin/init #39

hwdsl2 opened this issue Dec 29, 2022 · 1 comment

Comments

@hwdsl2
Copy link

hwdsl2 commented Dec 29, 2022

The latest version of rockylinux:9 image is missing /sbin/init (or /usr/sbin/init). Therefore the "Systemd integration" instructions do not work with the latest image version. See: https://hub.docker.com/r/rockylinux/rockylinux

I am aware that the official image is at https://hub.docker.com/_/rockylinux, I'm just linking to the systemd integration section in the link above.

This issue was found on Dec. 21, 2022. The Dec. 17 version of the rockylinux:9 image worked fine and has this file.

@NeilHanlon

Thank you for looking into this possible regression.

lfittl added a commit to pganalyze/collector that referenced this issue Jan 26, 2023
This was broken seemingly by accident, without any upstream updates as
of yet. Since we are also testing rhel9 this seems like a "nice to have"
and we can re-enable the test once the upstream issue is fixed.

See rocky-linux/sig-cloud-instance-images#39
lfittl added a commit to pganalyze/collector that referenced this issue Jan 27, 2023
…nit (#367)

This was broken seemingly by accident, without any upstream updates as
of yet. Since we are also testing rhel9 this seems like a "nice to have"
and we can re-enable the test once the upstream issue is fixed.

See rocky-linux/sig-cloud-instance-images#39
@NeilHanlon
Copy link
Member

Hi -

I apologize for the extreme latency on responding to this issue. I will investigate adding the init binary to the container in 8.8. It was removed while building the 8.7 images due to systemd polluting the build root and init not being actually a necessary component for most container users, due to container philosophy of running a single thing in a container.

We recognize that users do need/want init containers, and so I would recommend users who need init available use the ubi variants of the container images which provide the init/systemd binaries.

We also have a PR open to add ubi-micro and ubi-init variants, the latter of which would automatically have init set as an entrypoint. #42

@NeilHanlon NeilHanlon closed this as not planned Won't fix, can't repro, duplicate, stale Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants