Open sglebs opened 8 months ago
This image is designed to be run as root - Are you doing anything that would change the user context like user name spaces?
I'm available for custom development to make it NOT work this way.
I just deployed to Railway.app, which is an inexpensive cloud platform (like a mini heroku) and does not require expensive DevOps talent. Perhaps they do some wrapping that exposes this issue?
I can also try fly.io, which is another cloud platform for poor folks like me
I tried deploying to Dokku both with a custom Dockerfile and through Dokku's image deployment feature and got the same error: s6-overlay-suexec: fatal: can only run as pid 1
. I'm still tinkering with it and will update if I make any progress, otherwise I'll likely just try and run it directly on Docker.
Update: I was able to get it working after changing this option through Dokku: dokku scheduler-docker-local:set <APP_NAME> init-process false
.
I have a relatively surface level understanding of Dokku, but can confirm that deploying via dokku git:from-image <app_name> docker.io/tiredofit/freescout:latest
had the same error as above, and was fixed with the same command @matharvard entered. Thank you!
Edit: It may not have completed Initialization steps, however, as I look in the docker logs and it says 30-freescout did not pass completion check. Edit edit: May be my fault for not setting all the environment variables before trying to run it.
Summary
When deploying to Railway.app I get:
Steps to reproduce
Deploy to Railway.app
What is the expected correct behavior?
Locally/docker:
Relevant logs and/or screenshots
This is what I found that is relevant: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2765
It seems to be related to /init
Environment
Possible fixes
I tried this:
But it did not fix it.