-
Notifications
You must be signed in to change notification settings - Fork 319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
java.io.IOException: Read end dead permanently - master disconnects docker attached agents #581
Comments
Can you give more details on this build ? |
Same problem here since I migrated from "ssh key injection" to "attach". |
seems to be comparable issue with github.com/KostyaSha/yet-another-docker-plugin/pull/216/files/1c2e885d30bda0638e423c0df66489f7eaf2a5b3 |
@spbkelt as you exec into container, can you check with |
I've tested running a job to run endless Can you describe what's happening on your build at the time this issue occurs, so I can try to establish which condition trigger this error ? |
New logs:
I have general pipeline with stages where mvn command is running
Normally it takes more than 10 minutes overall. The longest one was 14 min
No
No |
Hi guys I have same issue when using windows docker agent via TCP socket and some observations here:
Dec 20, 2017 5:03:30 AM FINE com.github.dockerjava.core.command.AbstrDockerCmd exec |
@alexeygrigorovaurea this is by design for this "attach" connector : is uses docker interactive mode as a transport layer for jenkins remoting. Starting remoting agent detached require another transport protocol, either SSH or JNLP, to connect master with agent. Please note remoting channel is never inactive : PingThread do at least ensure some regular traffic. Also, I never noticed a container being killed for inactive interactive mode (I use this a lot). |
Hi @ndeloof , thanks for explanantion
|
jenkins: 2.73.3
docker-plugin: 1.0.4
We are facing constantly issue with disconnecting master -> agent
Jenkins master logs:
Docker container is live and running at the same time
I can even connect and run command inside it
The text was updated successfully, but these errors were encountered: