Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Component/s: docker-custom-build-environment-plugin
-
Labels:None
-
Environment:Plugin version 1.6.5
-
Similar Issues:
Description
Attachments
Activity
It is a fault of docker exec command:
kassner@w:~$ DOCKER_ID=$(docker run -d -it php:7.0 /bin/cat)
kassner@w:~$ docker exec -it ${DOCKER_ID} php -r "exit(2);"
kassner@w:~$ echo $?
129
kassner@w:~$ docker exec -i ${DOCKER_ID} php -r "exit(2);"
kassner@w:~$ echo $?
2
kassner@w:~$
Removing the tty from plugin's call avoids that, but I am not sure if we can just drop the TTY from it, even though it is non-interactive.
Rafael Kassner
added a comment - dan tran
It is a fault of docker exec command:
kassner@w:~$ DOCKER_ID=$(docker run -d -it php:7.0 /bin/cat)
kassner@w:~$ docker exec -it ${DOCKER_ID} php -r "exit(2);"
kassner@w:~$ echo $?
129
kassner@w:~$ docker exec -i ${DOCKER_ID} php -r "exit(2);"
kassner@w:~$ echo $?
2
kassner@w:~$
Removing the tty from plugin's call avoids that, but I am not sure if we can just drop the TTY from it, even though it is non-interactive. agree that -t is problematic. Thanks for the details
dan tran
added a comment - agree that -t is problematic. Thanks for the details Any action on this?
Supplying --tty makes it impossible to run repo inside a containerized job.
Keith Derrick
added a comment - Any action on this?
Supplying --tty makes it impossible to run repo inside a containerized job. The best solution would be to provide an option (per job) to disable provision of --tty
Keith Derrick
added a comment - The best solution would be to provide an option (per job) to disable provision of --tty 
I dont see this issue in my build, how exactly it fails on you env?