thielj

This should do it: https://github.com/thielj/docker-health-proxy/pkgs/container/docker-health-proxy It currently leaves the `/containers/json` API enabled to simplify testing with current U-K release. I suggest replacing this with `/_ping` which is also official Docker...

I've built the [final version (v1.0.0)](https://github.com/thielj/docker-health-proxy/pkgs/container/docker-health-proxy). It requires `/_ping` instead of `/containers/json?all=true` for the connection test. Or rather, you will get a 403 error when you hit Test, as it...

Regarding the docker remote setups you're recommending as "secure"... https://thehackernews.com/2024/06/commando-cat-cryptojacking-attacks.html

@ColCh The tecnativa proxy exposes far too much information, including for example secrets passed in environment variables, command line parameters, credentials for network mounts, etc. The nginx based proxy I...

@shalafi99 That's intended as the proxy also blocks the listing of all containers 🚧 I suggested that the Test button uses the official `/_ping` API call instead, which doesn't leak...

@CommanderStorm As I mentioned already, and others have mentioned before, letting something go into the pending state isn't really a solution if you have e.g. a job running once a...

Try a `docker inspect containername` and check the reported State.

A use case is for example container volumes. When they are detached, plain text passwords remain on the volume or the underlying storage system. The solution in many other projects...

It's unnecessary to encrypt heartbeats and events; but connection strings, authentication headers and such shouldn't be persisted in plaintext, as much as you don't store login passwords in plaintext. There's...

I didn't say "split the database"; you actually don't even need to change the database at all. Where you save plaintext strings now, you save encrypted bytes - base64 encoded...