Evaluation for a version with also write capabilities

[tiamilani]

Hi, first of all thank you very much for the nice work. I like the idea of using your docker socket proxy to first of all reduce memory footprint but also improve security.
I was wondering, would you be willing to have a version that also exposes the capability of perform write actions to the socket?

To support my case I have to use cases that I currently deploy on my system:

1. I use a docker backup system that I can control using labels, and it's convenient because it shouts down databases before saving a snapshot of the volumes associated with the DB.
2. I use also sablier to start and stop some containers that I only use maybe once a week and it's really convenient, but also in this case is required write access to the socket.

[11notes]

I was wondering, would you be willing to have a version that also exposes the capability of perform write actions to the socket?

Technically I have nothing against that, question is how to implement it. Apps like Portainer, Dockge and what they are all called will never work with this proxy, because they need to manipulate the entire Docker stack to work, but if an app just needs to stop and start existing containers, without the right to create new ones, that’s a valid use case and option for this kind of proxy. I’ll give it a go when I have time, I don’t know the Docker API by heart but it should only be a few endpoints and verbs that need to pass to allow start, stop of existing containers.

By the way. You don’t need to stop containers to take a backup of their volumes. For databases or other apps that keep data in RAM, you should always use their capabilities first, like in my 11notes/postgres image for instance. For the actual container data, reside your volumes on a CoW filesystem like XFS, and you can simply copy all data via reflink=always to another system, no need to stop or start anything.

[tiamilani]

Thank you very much, I'll be happy to give it a go in the future :)

Regarding the start and stop of containers this is exactly what sablier uses, or at least this is what I've noticed from my tests.

Thanks for the tip on databases also, I'm not well experienced with those but while I was setting up my strategy to backup important DBs I thought the most safest way was to gently shut the service(s) that where using/managing the DB and then backup the file.
But surely I still have to learn about those. Probably some times is enough to add a cron job that executes a command to safely backup the data. I.e. this is the command given in the vaultwarden wiki on how to safely backup the SQL Lite DB files sqlite3 data/db.sqlite3 ".backup '/path/to/backups/db-$(date '+%Y%m%d-%H%M').sqlite3'" I assume it would be enough to encapsulate it in a docker exec command.