docker-socket-proxy
Proxy over your Docker socket to restrict which requests it accepts (by Tecnativa)
shepherd
Docker swarm service for automatically updating your services whenever their image is refreshed (by containrrr)
Our great sponsors
docker-socket-proxy | shepherd | |
---|---|---|
23 | 6 | |
1,200 | 455 | |
6.8% | 2.9% | |
5.3 | 6.0 | |
12 days ago | 19 days ago | |
Python | Shell | |
Apache License 2.0 | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docker-socket-proxy
Posts with mentions or reviews of docker-socket-proxy.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-05.
-
Security for your Homeserver
I just found this the other day. You might be interested I haven't done myself yet https://github.com/Tecnativa/docker-socket-proxy
-
Gitea 1.19.0 released - now with support for Actions
I think you could provide access to the socket using a "docker-socket-proxy" container. It allows other containers to access the docker socket, you can even control which actions are allowed and which are not. You can use a bridge network for the communication to the socket-proxy container, so the socket-proxy container does not need to map/expose any ports. In the other container you need to set the "DOCKER_HOST" env variable accordingly, e.g. "DOCKER_HOST=tcp://mydockersockerproxycontainer:2375". https://github.com/Tecnativa/docker-socket-proxy
-
Unraid Remotely Access Docker Daemon
I use the container docker socket proxy
- Why does next cloud docker installation require access to /var/run/docker.sock (albeit read-only)? Is there a way to circumvent that?
-
Docker socket security
There are Docker socket proxys (like docker-socket-proxy 😉) that are made exactly for this. You can pass only read access to the socket and even restrict what resources can be read.
-
VM with multiple staging hosts GitLab CI?
So far I have Traefik set up and tested (along with some security lockdowns https://github.com/Tecnativa/docker-socket-proxy). This is working well: I can manually create containers, get a cert, dynamic hostnames, etc.
-
Is there any docker dashboard that auto detect the services ?
May be not necessarily: https://github.com/Tecnativa/docker-socket-proxy
-
[How-to] Securing access to your `docker.sock` file.
Many of you might already be familiar with Tecnativa's docker-socket-proxy which says:
-
Basic Traefik configuration tutorial
version: "3.7" services: traefik: image: traefik:v2.6 command: # Entrypoints configuration - --entrypoints.web.address=:80 # Docker provider configuration - --providers.docker=true # Makes sure that services have to explicitly direct Traefik to expose them - --providers.docker.exposedbydefault=false # Use the secure docker socket proxy - --providers.docker.endpoint=tcp://socket_proxy:2375 # Default docker network to use for connections to all containers - --providers.docker.network=traefik_public # Logging levels are DEBUG, PANIC, FATAL, ERROR, WARN, and INFO. - --log.level=info ports: - 80:80 networks: - traefik_public - socket_proxy restart: unless-stopped depends_on: - socket_proxy # https://github.com/traefik/whoami whoami: image: traefik/whoami:v1.7.1 labels: # Explicitly instruct Traefik to expose this service - traefik.enable=true # Router configuration ## Listen to the `web` entrypoint - traefik.http.routers.whoami_route.entrypoints=web ## Rule based on the Host of the request - traefik.http.routers.whoami_route.rule=Host(`whoami.karvounis.tutorial`) - traefik.http.routers.whoami_route.service=whoami_service # Service configuration ## 80 is the port that the whoami container is listening to - traefik.http.services.whoami_service.loadbalancer.server.port=80 networks: - traefik_public # https://github.com/Tecnativa/docker-socket-proxy # Security-enhanced proxy for the Docker Socket socket_proxy: image: tecnativa/docker-socket-proxy:latest restart: unless-stopped environment: NETWORKS: 1 SERVICES: 1 CONTAINERS: 1 TASKS: 1 volumes: - /var/run/docker.sock:/var/run/docker.sock:ro networks: - socket_proxy networks: traefik_public: external: true socket_proxy: external: true
- docker-socket-proxy - Proxy over your Docker socket to restrict which requests it accepts
shepherd
Posts with mentions or reviews of shepherd.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-04-20.
-
Docker Swarm: automatically update service when new image is released
Since watchtower doesn't support Docker Swarm I've come across shepherd but the author has stated that he wont be maintaining the project anymore which makes me reluctant to use it.
-
Reminder to do some docker maintenance
Shepherd for those of that run docker swarm.
- Watchtower with Docker Swarm?
-
Do you have auto update for your containers ? (with watchtower for example)
Not at production (there are strict versioned images), but personally I use Shepherd in my distributed Docker Swarm (many hosts in different locations, even different architectures). I wonder why people say about some terrible issues. I must be very lucky: for over a year usage I've had only single one problem when service wasn't properly restarted (I remember it was Traefik). The only services excluded from auto-update are PostgreSQL and MongoDB (MariaDB works fine with auto updates).
-
Docker image update notifier
Because all my Docker services are running in Docker Swarm I use similar project shepherd (available also at dockerhub). Not many features, but extremely easy to set up and it does its job (check, download and restart any service when new image is available, so I don't need to care about program updating at all).
-
Is Watchtower abandoned ? Is there a better alternative?
I've used this for years
What are some alternatives?
When comparing docker-socket-proxy and shepherd you can also consider the following projects:
watchtower - A process for automating Docker container base image updates.
Diun - Receive notifications when an image is updated on a Docker registry
wireguard-ui - Wireguard web interface
docker-image-update-notification - If you have (many) docker images on your server(s) and want to always be updated, this script will help you check them periodically
cadvisor - Analyzes resource usage and performance characteristics of running containers.
ouroboros - Automatically update running docker containers with newest available image
flap
docker - â›´ Docker image of Nextcloud
docker-swarm - docker-swarm, nginxproxymanager, portainer, wordpress
docker-socket-proxy vs watchtower
shepherd vs watchtower
docker-socket-proxy vs Diun
shepherd vs Diun
docker-socket-proxy vs wireguard-ui
shepherd vs docker-image-update-notification
docker-socket-proxy vs cadvisor
shepherd vs ouroboros
docker-socket-proxy vs flap
shepherd vs flap
docker-socket-proxy vs docker
shepherd vs docker-swarm