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 #23

Open
TechnoDezi opened this issue Nov 9, 2022 · 4 comments
Open

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

TechnoDezi opened this issue Nov 9, 2022 · 4 comments
Labels

Comments

@TechnoDezi
Copy link

Summary

When attempting to run tiredofit/clamav:latest on Azure Container Instance I get the error "s6-overlay-suexec: fatal: can only run as pid 1" as the container is starting and then it never starts successfully.
The Version from 2021/04 seems to start fine, but clamAV is too out datated and can't download files.

Steps to reproduce

Add a container instance on Azure and set it up to use tiredofit/clamav:latest.

What is the expected correct behavior?

The container should start, load clam AV and update virus database.

@TechnoDezi TechnoDezi added the bug label Nov 9, 2022
@tiredofit
Copy link
Owner

I believe this is related to the upgrade of S6 Overlay from 2.x to 3.x in the base images.

Are you trying to launch this container as a scoped user?

@TechnoDezi
Copy link
Author

Hi

Sorry for the delay. I think it must be yes. I'm not sure how Azure container instances start the container, but it's very likely scoped user.

@makschr
Copy link

makschr commented Nov 30, 2022

Hi,
Any suggestion with this?
We are experiencing the same problem. Last version successfully run on Azure is 2.3.1.

@JonSmith
Copy link

JonSmith commented Dec 1, 2022

Same problem here - pulling the 2.3.1 image from Docker into an Azure Container Instance works but any later image fails with the "s6-overlay-suexec: fatal: can only run as pid 1" error. Going back to the Alpine base, the 3.5-7.2.19 image works and 3.5-7.3.0 fails with the same error - the version where S6 was changed from 2 to 3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants