Skip to content
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

Docker v26 support (TLS mandatory now) #600

Open
gabrielmocan opened this issue Mar 25, 2024 · 2 comments
Open

Docker v26 support (TLS mandatory now) #600

gabrielmocan opened this issue Mar 25, 2024 · 2 comments

Comments

@gabrielmocan
Copy link

As of Docker v26 release, TLS is now mandatory to connect to the docker socket.

Source: https://docs.docker.com/engine/release-notes/26.0/

Deprecate the ability to accept remote TCP connections without TLS. [Deprecation notice](https://github.com/docker/cli/tree/v26.0.0/deprecation.md#unauthenticated-tcp-connections) [docker/cli#4928](https://github.com/docker/cli/pull/4928) [moby/moby#47556](https://github.com/moby/moby/pull/47556).

Any plans to support this breaking change?

@francislavoie
Copy link
Collaborator

The vast majority of users should be using a unix socket anyway. What usecase do you see for needing to use TCP?

@hongkongkiwi
Copy link

The vast majority of users should be using a unix socket anyway. What usecase do you see for needing to use TCP?

Getting Caddy to populate entries from docker hosts on the local network. In theory you can use controller and server for this, but there's definitely legitimate reasons for doing this over TCP in a local lan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants