-
Notifications
You must be signed in to change notification settings - Fork 12
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
Custom command for containers not working #476
Comments
mattiaswal
added a commit
that referenced
this issue
Jun 15, 2024
This made it impossible to use the "command" in container configuration. This fix issue #476
mattiaswal
added a commit
that referenced
this issue
Jun 17, 2024
This made it impossible to use the "command" in container configuration. This fix issue #476
13 tasks
mattiaswal
added a commit
that referenced
this issue
Jun 17, 2024
This made it impossible to use the "command" in container configuration. This fix issue #476
mattiaswal
added a commit
that referenced
this issue
Jun 17, 2024
This made it impossible to use the "command" in container configuration. This fix issue #476
mattiaswal
added a commit
that referenced
this issue
Jun 19, 2024
This made it impossible to use the "command" in container configuration. This fix issue #476
mattiaswal
added a commit
that referenced
this issue
Jun 19, 2024
This made it impossible to use the "command" in container configuration. This fix issue #476
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Setting up a container with a custom command does not seem to be working properly:
The log shows:
Finit tries to restart it 10 times and then gives up.
Calling
container -n httpd start
(same as Finit) gives the following output:Creating another container, using the same command, and manually starting it, works:
Even connecting to httpd on port 8080 from the outside works:
The text was updated successfully, but these errors were encountered: