Skip to content

'Certificate path doesn't exist' when using DOCKER_HOST=unix:///var/run/docker.sock #480

@francisdb

Description

@francisdb

Switched to 3.0.0-RC1 after #419 was fixed
But now the config builder fails with setting
export DOCKER_HOST=unix:///var/run/docker.sock

DockerClientConfig.createDefaultConfigBuilder().build()

com.github.dockerjava.api.exception.DockerClientException: Certificate path (DOCKER_CERT_PATH) '/var/lib/jenkins/.docker/certs' doesn't exist. (DockerClientConfig.java:112)
[error] com.github.dockerjava.core.DockerClientConfig.checkDockerCertPath(DockerClientConfig.java:112)
[error] com.github.dockerjava.core.DockerClientConfig.<init>(DockerClientConfig.java:85)
[error] com.github.dockerjava.core.DockerClientConfig$DockerClientConfigBuilder.build(DockerClientConfig.java:431)
[error] com.whisk.docker.DockerKit$class.$init$(DockerKit.scala:10)

Am I correct that for sock communication there is no need for the certificate path check? At least on 2.x this used to work.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions