Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
alobato found that inside fails with a cryptic error when trying to run images specifying ENTRYPOINT. For example this causes this to fail, which is confusing since for purposes of using Image.inside it makes no sense to be running copy_reference_files and associated code; the way this image is normally designed to work for command-line execution is inappropriate.
Attachments
Issue Links
- is duplicated by
-
JENKINS-39485 withContainerStep fails if using entrypoint in DockerFile
-
- Resolved
-
- relates to
-
JENKINS-41316 docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
-
- Reopened
-
-
JENKINS-39748 Since 37987 images that use ENTRYPOINT for a reason cannot be used in testing
-
- In Review
-
- links to
It's not much nicer but as a workaround you can do:
This then has the same behavior as docker.image().inside() as before with ENTRYPOINT being executed (so things like systemd or a similar reaper will run) ...
There's also
JENKINS-26178of course to be able to exec in a running container which would work around this, if it gets implemented.