Tecnativa / Tecnativa/docker-socket-proxy
Could I to use the docker-socket-proxy with a password to tcp?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.8k
- Forks
- 207
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I'm using docker-socket-proxy with a host network (internal, not accessible externally) and getting this tcp inside a containers like traefik and portainer.. I could not to set an internal network connection only for these containers because I'm using a normal container with this docker socket to a container with swarm (I don't know how connect a network between a normal container and a swarm node without to use the host network (not accessible externally). so the other containers can acess the tcp connection too.
Could I to use the docker-socket-proxy with a password to this tcp connection?
Best regards,
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names docker-socket-proxy, its TCP connection, and Docker Swarm alongside Traefik and Portainer, but no repository file or test. Start by tracing how the proxy exposes the Docker socket over TCP and how authentication is configured; done should be a clearly specified and tested way to protect that connection with a password.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- authentication, infrastructure, networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100