You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, only target_image context supports the setup of the entrypoint, which is affects only "production" image.
In cases, where base image already has an entrypoint, ansible-bender will stuck during the build, due endless process running by container.
This problem can be solved by adding the ability to setup entrypoint for working container , this entrypoint will override the entrypoint of the base image:
I made a pull request (#232 ) that will add the option of setting entrypoint for working_container. This at least solves my problem with getting stuck during the build phase.
Currently, only target_image context supports the setup of the entrypoint, which is affects only "production" image.
In cases, where base image already has an entrypoint, ansible-bender will stuck during the build, due endless process running by container.
This problem can be solved by adding the ability to setup entrypoint for working container , this entrypoint will override the entrypoint of the base image:
The text was updated successfully, but these errors were encountered: