Skip to main content
8 events
when toggle format what by license comment
Mar 11 at 14:52 comment added Jack (I prefer not to expose the Docker TCP socket on localhost, as it feels insecure for me. This configuration allows all processes to access it without any access control.)
Mar 11 at 14:41 comment added Jack I also had the idea of running wollomatic/socket-proxy on the main host within the Docker environment (which I wanted to try anyway) and then exposing it as a TCP socket over SSH. Ideally, I would like a solution that allows me to connect a Podman network and a Docker network over SSH. This way, I can easily add the TCP socket and the Podman containers that need access to the Docker socket to the network. Do you have any suggestions on how to achieve this and whether it's a good idea?
Mar 11 at 14:29 comment added Jack I also tried to avoid using SSHFS and attempted to mount the Unix socket over SSH, but I still can't access the socket. :( Perhaps Podman is still a bit buggy? (stackoverflow.com/q/60683674)
Mar 11 at 14:26 comment added Jack @wobtax Yes, I am using a running docker daemon on my main host and want to use podman on my secondary host. The secondary host intended for performing backups, which shall then not be reachable from the main host. The image offen/docker-volume-backup is a docker image and which I wish to let (read) access the /var/run/docker.sock on the main host. (Offsite Backup)
Feb 28 at 18:09 comment added wobtax And, to be clear, the docker daemon is running, right? It sounds like you have a docker (not podman) setup, but want to use this podman image (not docker) to perform these backups.
Feb 21 at 17:22 history edited ReflectYourCharacter CC BY-SA 4.0
deleted 26 characters in body
S Feb 21 at 17:05 review First questions
Mar 7 at 15:00
S Feb 21 at 17:05 history asked Jack CC BY-SA 4.0