i hate containers.
-
i hate containers.
today: podman doesn’t want to route shit correctly when you expose a container port on host port 80. just. “no route to host”. good shit. 8080? works fine. Ipv4/v6? works fine. port 80? fuck you. how about you waste 2 hours of your life.
docker was such a fucking mistake, we should return to normal amounts of network namespaces and jails
-
i hate containers.
today: podman doesn’t want to route shit correctly when you expose a container port on host port 80. just. “no route to host”. good shit. 8080? works fine. Ipv4/v6? works fine. port 80? fuck you. how about you waste 2 hours of your life.
docker was such a fucking mistake, we should return to normal amounts of network namespaces and jails
Possibly because it's a port <1024 and you are running it "rootless" without CAP_NET_BIND_SERVICE?
-
i hate containers.
today: podman doesn’t want to route shit correctly when you expose a container port on host port 80. just. “no route to host”. good shit. 8080? works fine. Ipv4/v6? works fine. port 80? fuck you. how about you waste 2 hours of your life.
docker was such a fucking mistake, we should return to normal amounts of network namespaces and jails
@filmroellchen systemd services my beloved and behated
-
i hate containers.
today: podman doesn’t want to route shit correctly when you expose a container port on host port 80. just. “no route to host”. good shit. 8080? works fine. Ipv4/v6? works fine. port 80? fuck you. how about you waste 2 hours of your life.
docker was such a fucking mistake, we should return to normal amounts of network namespaces and jails
@filmroellchen Any SElinux interactions preventing route creation?
-
R relay@relay.an.exchange shared this topic
