compose: OpenSSL version mismatch. Built against 1010106f, you have 101000cf
Description of the issue
Error when using docker-compose exec
with DOCKER_HOST=ssh://...
Context information (for bug reports)
Output of docker-compose version
docker-compose version 1.26.2, build eefe0d31
docker-py version: 4.2.2
CPython version: 3.7.7
OpenSSL version: OpenSSL 1.1.0l 10 Sep 2019
Output of docker version
Client: Docker Engine - Community
Version: 19.03.12
API version: 1.40
Go version: go1.13.10
Git commit: 48a66213fe
Built: Mon Jun 22 15:45:36 2020
OS/Arch: linux/amd64
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 19.03.12
API version: 1.40 (minimum version 1.12)
Go version: go1.13.10
Git commit: 48a66213fe
Built: Mon Jun 22 15:49:27 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v1.2.13
GitCommit: 7ad184331fa3e55e52b890ea95e65ba581ae3429
runc:
Version: 1.0.0-rc10
GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version: 0.18.0
GitCommit: fec3683
Output of docker-compose config
version: '3'
services:
portainer:
image: portainer/portainer:1.24.1
command: -H unix:///var/run/docker.sock
volumes:
- data:/data
- /var/run/docker.sock:/var/run/docker.sock
restart: unless-stopped
volumes:
data:
Steps to reproduce the issue
- create a
.env
file and addDOCKER_HOST=ssh://...
with a valid ssh host with docker engine docker-compose up -d
docker-compose exec portainer bash
Observed result
error during connect: Get http://docker/v1.40/containers/a1a823ab0e6b66087bf0fd609c34da5e70c23446cf19791f66d6bf277f14f89a/json: command [ssh -- example.org docker system dial-stdio] has exited with exit status 255, please make sure the URL is valid, and Docker 18.09 or later
is installed on the remote host: stderr=OpenSSL version mismatch. Built against 1010106f, you have 101000cf
Expected result
Open a bash terminal in the portainer
container on the remote docker engine.
Stacktrace / full error message
error during connect: Get http://docker/v1.40/containers/a1a823ab0e6b66087bf0fd609c34da5e70c23446cf19791f66d6bf277f14f89a/json: command [ssh -- example.org docker system dial-stdio] has exited with exit status 255, please make sure the URL is valid, and Docker 18.09 or later
is installed on the remote host: stderr=OpenSSL version mismatch. Built against 1010106f, you have 101000cf
Additional information
OS version / distribution, docker-compose
install method, etc.
Running on WSL 2 Ubuntu on windows 10. The docker-compose is the one mounted from docker desktop.
But I also tested with a native linux machine.
I tested with two remote hosts, one google vm and one raspberry pi. On the google vm:
Client:
Version: 19.03.6
API version: 1.40
Go version: go1.13.5
Git commit: 369ce74
Built: Tue May 19 10:01:57 2020
OS/Arch: linux/amd64
Experimental: false
Server:
Engine:
Version: 19.03.6
API version: 1.40 (minimum version 1.12)
Go version: go1.13.5
Git commit: 369ce74
Built: Tue May 19 10:00:30 2020
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.3.2
GitCommit: ff48f57fc83a8c44cf4ad5d672424a98ba37ded6
runc:
Version: 1.0.0-rc10
GitCommit:
docker-init:
Version: 0.18.0
GitCommit: fec3683b971d9c3ef73f284f176672c44b448662
On the raspberrypi:
Client: Docker Engine - Community
Version: 19.03.12
API version: 1.40
Go version: go1.13.10
Git commit: 48a6621
Built: Mon Jun 22 15:53:41 2020
OS/Arch: linux/arm
Experimental: false
Server: Docker Engine - Community
Engine:
Version: 19.03.12
API version: 1.40 (minimum version 1.12)
Go version: go1.13.10
Git commit: 48a6621
Built: Mon Jun 22 15:47:34 2020
OS/Arch: linux/arm
Experimental: false
containerd:
Version: 1.2.13
GitCommit: 7ad184331fa3e55e52b890ea95e65ba581ae3429
runc:
Version: 1.0.0-rc10
GitCommit: dc9208a3303feef5b3839f4323d9beb36df0a9dd
docker-init:
Version: 0.18.0
GitCommit: fec3683
I also tested with older docker compose version 1.25.5 and the newer 1.27.0-rc1.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 13
- Comments: 26 (2 by maintainers)
Commits related to this issue
- workaround for docker-compose in CI https://github.com/docker/compose/issues/7686 — committed to Bigstool/group-management-system by 4piu 3 years ago
- workaround for docker-compose in CI https://github.com/docker/compose/issues/7686 — committed to Bigstool/group-management-system by deleted user 3 years ago
- Forcing installation of docker compose See for more info: https://github.com/docker/compose/issues/7686 — committed to ministryofjustice/fb-metadata-api by tomas-stefano 3 years ago
- Forcing installation of docker compose See for more info: https://github.com/docker/compose/issues/7686 — committed to ministryofjustice/fb-metadata-api by tomas-stefano 3 years ago
- Forcing installation of docker compose See for more info: https://github.com/docker/compose/issues/7686 — committed to ministryofjustice/fb-metadata-api by tomas-stefano 3 years ago
- Downgrade ubuntu agent version to fix OpenSSL bug https://github.com/docker/compose/issues/7686#issuecomment-877531508 — committed to swilliams96/shopkeepers-quiz-api by swilliams96 3 years ago
- Downgrade ubuntu agent version to fix OpenSSL bug https://github.com/docker/compose/issues/7686#issuecomment-877531508 — committed to swilliams96/shopkeepers-quiz-api by swilliams96 3 years ago
I’m seeing this using 1.29.2.
As a workaround you can install docker-compose from PIP.
@aiordache Please reopen, this issue is not fixed, neither in 1.28.5 nor 1.28.6
This happened to me on
github actions
. I solved by fixing ubuntu version.runs-on: ubuntu-latest
->runs-on: ubuntu-18.04
ubuntu-latest version has changed 18.04 to 20.04. Along with this, docker-compose verion has been updated, and updated dokcer-compose cause this error.It does not work with
1.29.1
Workaround: downgrade to 1.28.0.
Still happening in
1.29.1
Still experiencing this on 1.29.2 as well.
Local host: docker-compose version 1.29.2, build 5becea4 Docker version 20.10.0, build 7287ab3
Remote host: Docker version 20.10.7, build f0df350 (running in Swarm mode, for what that’s worth)
This is also impacting workflows in Github actions as @NoharaMasato said, which are also using v1.29.2.
Can confirm that had the exact same issue with
1.28.2
but1.28.0
worked fine. Downloaded releases directly from github.This bug still exists; I had to downgrade to 1.27.1 today after hours of failed troubleshooting
Why is this issue closed? I have docker-compose version 1.28.5, build c4eb3a1f on Windows WSL2 and get this error now.
Hi all, I’d recommend upgrading to Compose v2 as it will not have this issue. You can find the downloads on the release page: https://github.com/docker/compose/releases
You can either use it standalone or as a CLI plugin.
I can reproduce the same behavior on Ubuntu 20.04:
OS Version
Output of docker-compose version
Result
Any chance @chris-crone to fix the issue without using pip approach?