init fix or possible explanation

[peterducai]

hi all. As RHEL/Fedora guy i stopped using docker some time ago so i tried to replace docker command with podman, but running with --init it gives me error

podman run -it --init -p 3000:3000 -v "$(pwd):/home/project:cached" theiaide/theia:next
Error: please specify a path to the container-init binary

but when running

podman run -it -p 3000:3000 -v "$(pwd):/home/project:cached" theiaide/theia:next

it starts fine and I can see IDE.

can you explain error and what --init suppose to do? thanks

[vince-fugnitto]

@peterducai I found the following information:

From the docker documentation, it states that --init is used to specify the init process:

You can use the --init flag to indicate that an init process should be used as the PID 1 in the container. Specifying an init process ensures the usual responsibilities of an init system, such as reaping zombie processes, are performed inside the created container.

The default init process used is the first docker-init executable found in the system path of the Docker daemon process. This docker-init binary, included in the default installation, is backed by tini.

In addition, there is an issue for podman which describes a similar problem as you've reported:
containers/podman#1670

[marcdumais-work]

@peterducai

Please see #196 (corresponding issue: #195)) for more info about us adding --init switch to our documentation and what it does.

It seems that podman needs to bundle tini or equivalent like docker, for the switch to work: containers/podman#4159

[stale]

This contribution has been automatically marked as stale due to inactivity, and it will be closed if no further activity occurs. Thank you for contributing to Theia!