-
Notifications
You must be signed in to change notification settings - Fork 424
Open
Description
Given a pipeline with a custom `DOCKER_HOST`:
node {
stage('Testing LIMA VM') {
docker.withServer('unix:///home/user/.lima/lima-test/sock/docker.sock') {
docker.image('jenkins/agent').inside {
sshagent(['user_b']) {
sh 'ssh-add -l'
}
}
}
}
}
I get this error:
ERROR: Failed to run ssh-agent: Error response from daemon: No such container: 85b4f32a54d1292....
I've investigated the issue and I think that
docker-workflow-plugin/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java
Line 263 in 19b84d6
| @Override public Proc launch(Launcher.ProcStarter starter) throws IOException { |
Originally reported by jmdesprez, imported from: docker-workflow doesn't set DOCKER_HOST
- status: Open
- priority: Minor
- component(s): docker-workflow-plugin
- resolution: Unresolved
- votes: 0
- watchers: 2
- imported: 2025-12-07
Raw content of original issue
Given a pipeline with a custom `DOCKER_HOST`:
node { stage('Testing LIMA VM') { docker.withServer('unix:///home/user/.lima/lima-test/sock/docker.sock') { docker.image('jenkins/agent').inside { sshagent(['user_b']) { sh 'ssh-add -l' } } } } }I get this error: ERROR: Failed to run ssh-agent: Error response from daemon: No such container: 85b4f32a54d1292....
I've investigated the issue and I think that
should inject `DOCKER_HOST` into the `starter` envs (using the value from `envHost`)docker-workflow-plugin/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java
Line 263 in 19b84d6
@Override public Proc launch(Launcher.ProcStarter starter) throws IOException {
Reactions are currently unavailable