Use docker-socket-proxy to grant secure access to the docker socket #80
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
https://github.com/Tecnativa/docker-socket-proxy
Services currently using the docker socket:
Not all of these need the proxy.
assigned to @Jafner
We should implement this for both Jafner.net and Jafner.tools. Both for security reasons, and to enable homepage to remotely read the docker socket for health info in its service widgets.
mentioned in commit
91549029cc
mentioned in commit
a0b569b8c7
mentioned in commit
28cd1721b0
mentioned in commit
7bc6aa2c68
mentioned in commit
4c30b3e258
mentioned in commit
2001773642
mentioned in commit
cf4e8d1f59
changed the description
All done and good to go for homepage.
So we can split the containers using the socket into two categories: those who only need to read, and those who need full control.
Next we'll do exporter-docker and Traefik.
mentioned in commit
f781676d13
changed the description
marked the checklist item Jafner.net/homepage_homepage as incomplete
changed the description
changed the description
This is not a useful security layer for us.