mikeconrad/DocKetProxy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Mention limited testing

Browse Source
This commit is contained in:
Mike Conrad
2025-06-03 19:49:58 -04:00
parent ce4318d38b
commit a719d19968
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -1,4 +1,4 @@
# Docker Socket Proxy
# DocKet Proxy - Docker Socket Proxy
## Description
I wanted an easy/simple and secure way to use Traefik in my homelab without giving it free reign over my host machine and the Docker socket. This project is a WIP where I am testing out some concepts and ideas.
@ -37,4 +37,6 @@ $ curl -X POST localhost:8000/$DOCKER_API_VERSION/networks/create -H 'content-ty
Forbidden
```
See the full code for the list of routes that are allowed. Any not in the allow list are blocked by default.
See the full code for the list of routes that are allowed. Any not in the allow list are blocked by default.
I have done some limited testing with the latest version of Traefik and have not noticed any issues. I have another project that uses [Sablier Plugin](https://hub.docker.com/r/sablierapp/sablier) for Traefik and I have done some limited testing with that. I can confirm that `Sablier` is still able to start my containers, it looks like it may have some issues stopping all containers but I haven't fully explored it yet. That part of the reason why there is still some ugly logging in place.