-
New Feature
-
Resolution: Unresolved
-
Major
-
None
The fix for the issues with maven in JENKINS-37987 broke workflows that have images where the container is run and the ENTRYPOINT is epxecxted to be used... one example being a container with systemd
there should be a way to do something like:
docker.image('foo').inside { sh 'make test' }
and have the ENTRYPOINT still run
- is duplicated by
-
JENKINS-54389 Containers with ENTRYPOINT is not started correctly
- Open
-
JENKINS-41316 docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
- Reopened
-
JENKINS-49278 cat command in docker agents not detected correctly
- Reopened
-
JENKINS-40168 Make the override of ENTRYPOINT by image.inside optional
- Resolved
- relates to
-
JENKINS-37987 Image.inside fails for images specifying ENTRYPOINT
- Resolved
-
JENKINS-41316 docker.image('my-image').inside{...} no longer honors Dockerfile "entrypoint" since version 1.8
- Reopened
-
JENKINS-40170 Separate execution functionality of image.inside() into distinct steps
- Open
-
JENKINS-38438 image.inside { ... } does not create full configured user account
- Open