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

s6-overlay-suexec: fatal: can only run as pid 1 on Container start. #80

Open
mastertIT opened this issue Dec 17, 2022 · 2 comments
Open

Comments

@mastertIT
Copy link

mastertIT commented Dec 17, 2022

It seems the container exhibits this issue on starts now.

s6-overlay-suexec: fatal: can only run as pid 1
s6-overlay-suexec: fatal: can only run as pid 1

tried setting GUID and PUID as environment variables with no success.

@Nico640
Copy link
Owner

Nico640 commented Dec 18, 2022

Hi,

PUID / PGID environment variables only control the user / group used for running UISP inside the container, but the s6 supervisor should always run as PID 1 inside the container, which it is apparently not in your case. What command do you use to start the container (if you use docker compose please post the compose file content)?

@mastertIT
Copy link
Author

We don't pass any special commands on run. The issue first occurred when upgrading to the new container version. (believe the version of s6 has changed since the last time container was built)
We have no way of passing init=false either.
Running the container via admiral on vSphere.

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