[FEAT] Add CONTAINER_ID as filter
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- docker
- Domain
- infrastructure, security
Research direction
Start by reading the repository's existing request-filter configuration and the discussions in issues #12 and #13 to understand the prior decision. Done means the CONTAINER_ID setting clearly enables or disables /containers/{id}/ while preserving the proxy's security boundaries; the issue names no tests or files to run.
Written by the indexing model from the issue text.
Description
Is this a new feature request?
- I have searched the existing issues
Wanted change
I'd like to introduce the CONTAINER_ID parameter as filter. This parameter needs to enable/disable the /containers/{id}/ endpoint.
Reason for change
This suggestion has been discussed in the past see #12 and #13 in 2024, however the treat landscape keeps changing and as adoption of this solution is picking up its becoming more relevant.
Today this container is being used often with solutions such as Traefik resulting in near public exposure of the socket-proxy. The /containers/{id}/ endpoint allows access to sensitive endpoint such as the ENV variables of a container. Therefore I'd like to ask you to reconsider earlier position as stated in the issues #12 and #13 and add this feature.
Proposed code change
No response
- Dominant language
- Dockerfile
- Stars
- 317
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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.
More from linuxserver/docker-socket-proxy
-
enhancement no-issue-activity
Difficulty 4/5 3-5 days Newbie friendliness 52/100
linuxserver/docker-socket-proxy#45 · 4 comments ·
All issues in linuxserver/docker-socket-proxy
Similar issues
-
A cancelled tests run makes the coverage comment workflow fail and reports it as a red check on main Openarea: ci bug perceived difficulty: 3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Nitjsefnie-Harness-Commons/daedalus#921 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
crossplane/crossplane#7859 ·
-
Product: Terraform (AVM) Topic: Networking (HS) :globe_with_meridians:
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Azure/Azure-Landing-Zones#4282 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
bug carvel-triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
carvel-dev/kapp-controller#1861 ·