Tecnativa / Tecnativa/docker-socket-proxy
Different permissions for different containers
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.8k
- Forks
- 207
- PR merge metrics
- No merged PRs in 30d
Description
I know how to use this with traefik. I've found some samples how to use it with portainer.
But on a single server I'm using both traefik and portainer. That means I must expose many endpoints (because portainer wants them), and traefik therefore sees them too. From the samples I've seen, that includes the very powerful POST.
Is this the correct approach - or can I set different permissions for different containers?
If not currently possible, please consider this a feature request?
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
Start by reviewing the proxy's current permission configuration and the Docker API access needed by Traefik and Portainer, especially the POST endpoint mentioned in the issue. Determine whether permissions can be scoped separately per container; done means a clearly defined way for both containers to use the proxy without exposing unnecessary endpoints.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100