ufw-docker VS Moby

I am running ubuntu server 22.04 LTS and have fail2ban running on the host. This works great, no issues and IPs get banned for the rules I have in place. I am using UFW and have updated my after.rules for docker based on the recommendations here.

I use this without problems for Long time, https://github.com/chaifeng/ufw-docker

[2016]

A solution is known and formed detailed here: https://github.com/chaifeng/ufw-docker

In any case, maybe try to compare the blocked port ranges with the ports you are using. Did you see this https://github.com/chaifeng/ufw-docker

https://github.com/chaifeng/ufw-docker For example.

ufw is nice, when you are on public networks. And very nice if you are playing with SSH-Server, Docker,.. on your notebook. Couse you write coding, I want to add this, if you use docker.

You can use use this for a more manual approach: https://github.com/chaifeng/ufw-docker

Sorry that's about the extent of my docker network knowledge. One other thing you can check though - are you running ufw on the host? If so you can try updating the config with ufw-docker.

Hi! I'm also new to the homelab category, but I have a bit of experience. I'm currently running Ubuntu 22.04, and the only problem what I had is docker containers not working with ufw. (Fix can be found here: https://github.com/chaifeng/ufw-docker) I've been running my stuff in Docker containers, and it worked pretty well for me. So if you are also new to this, I'd definetly recommend Ubuntu for its simplicity. (Also tons of already great tutorials on how to do literally anything)

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...