docker-gen VS Moby

Yeah, I usually do if I pass URLs to container. But again, the nginx config is completely auto-generated by docker-gen. Not sure why they don't use the container name, maybe duplicate container names? (if that's possible)

I've not got around to it, but I've always fancied creating a nice landing page that automatically updates as services come up/down, using the system jwilder created to make nginx-proxy, docker-gen. Could be a fun little project, anyway!

https://github.com/nginx-proxy/acme-companion https://github.com/nginx-proxy/docker-gen https://github.com/projectdiscovery/dnsx https://github.com/projectdiscovery/httpx https://github.com/projectdiscovery/mapcidr https://github.com/debauchee/barrier https://github.com/stedolan/jq https://github.com/ddosify/ddosify https://github.com/kubernetes-sigs/kind https://github.com/mailcow/mailcow-dockerized https://github.com/motiv-labs/janus

Then to make deployment super easy we're using nginx-proxy which uses docker-gen (and the acme-companion for automatic SSL cert generation) to automatically re-configure an nginx reverse proxy to point to your containers.

I've now got a setup using docker where the reverse proxy configuration is within the container's configuration (using nginx-proxy, which uses docker-gen). That way I just set the host, path, etc. in my container config, deploy, and the nginx servers are re-configured accordingly. No need to worry about ports and IPs then either.

I use an automated nginx reverse proxy. What this does is setup an nginx reverse proxy which uses docker-gen (follow the advice of setting it up separately). docker-gen listens for docker events such as a container being run, inspects that container for the details it needs (port, host, etc.) then configures the nginx accordingly.

Having been featured in our February 2023, and January 2024 Release Radars, Moby is the original Linux Container runtime. This new version adds a bunch of changes to the Docker CLI and Moby itself with additional features. There's bug fixes and enhancements, with the main thing for users to be on the look out for containers that were created using Docker Engine 25.0.0. These containers might have duplicate MAC addresses, and thus must be recreated. The same goes for those containers created with Moby 25.0+ and with user defined MAC addresses. Read up on all these changes in the release notes.

Formlabs does this as well for their 3d printers, my earliest encounter of this was when Docker started getting popular: https://github.com/moby/moby/blob/master/pkg/namesgenerator/...

Try to use moby instead since that is the engine in Docker.

https://github.com/moby/moby

> Podman is designed to help with this by providing stronger default security settings compared to Docker. Features like rootless containers, user namespaces, and seccomp profiles, while available in Docker, aren't enabled by default and often require extra setup.

Seccomp has been enabled by default since 2015: https://github.com/moby/moby/pull/18780

It is true that Rootless isn't enabled by default but its "extra setup" can be done with a single command (`dockerd-rootless-setuptool.sh install`)

Perhaps.

Thing is, https://github.com/moby/moby/blob/670bc0a46c4ca03b75f1e72f73... is using https://github.com/mistifyio/go-zfs which features code like `out, err := zfsOutput("get", "-H", key, d.Name)` (Source: https://github.com/mistifyio/go-zfs/blob/master/zfs.go#L315) to get a single zfs property.

Somebody chose to use a library as abstraction that looks good but is implemented as a MVP (nothing wrong with that). "In the future, we hope to work directly with libzfs" should have raised an alarm somewhere, though.

AppArmor can restrict /proc and this is even used by docker: https://github.com/moby/moby/blob/master/contrib/apparmor/te...