Allow setting entrypoint on container image

The new feature for running commands inside a container is awesome. However, lots of images specify entrypoints that need to be overriden for commands to work without modifications. Imho its important to be able to override this so that Octopus can use the any container. Please add an “entrypoint” option to the dialog where registry and image are configured.

Hi @trond,

Thanks for reaching out. I will pass this along as a suggestion to the appropriate people here at Octopus.

Thanks,
Jeremy

Hi @trond,

Also as a workaround you could create a new image based on the one you want, specify the entrypoint in the Dockerfile for that image and use that as the execution container. You may already be doing this but wanted to give you another option.

Please let me know if you have any questions.

Thanks,
Jeremy

thanks,
yup the workaround is valid, if somewhat cumbersome.

Hi @trond,

You’re welcome. Yeah, it definitely isn’t ideal. I just wanted to give you an option in case you weren’t aware of it while the feature team takes a look at your suggestion.

Please reach out in the meantime with any questions or concerns.

Thanks,
Jeremy

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.