edu4rdshl/edu4rdshl.github.io
1
0
Fork 0
mirror of https://github.com/edu4rdshl/edu4rdshl.github.io.git synced 2026-07-17 23:24:49 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

(post-update): From Docker to Podman: full migration to rootless.

Browse source 
Clarify the network section.
This commit is contained in:
Eduard Tolosa 2025-02-21 20:00:23 +00:00
parent 590e2b7467
commit cc04d2c6b4
2 changed files with 12 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

6
.devcontainer/devcontainer.json
View file

@ -26,6 +26,10 @@
] ]
} }
}, },
"runArgs": ["--restart=always", "--name=Jekyll-blog"], "runArgs": [
"--network=development",
"--restart=always",
"--name=Jekyll-blog"
],
"remoteUser": "root" "remoteUser": "root"
} }

11
_posts/2025-02-21-from-docker-to-podman-full-migration-to-rootless.md
View file

@ -295,8 +295,8 @@ After migrating from Docker to Podman, you may encounter some issues:
Some minor but still annoying issues: Some minor but still annoying issues:
- The system journal will gets spammed with [porman-events](https://docs.podman.io/en/stable/markdown/podman-events.1.html) messages. The only way to disable them is to set `events_logger = "none"` in `~/.config/containers/containers.conf`, but then you won't be able to use `podman container logs`, which is a big downside. - The system journal will gets spammed with [podman-events](https://docs.podman.io/en/stable/markdown/podman-events.1.html) messages. The only way to disable them is to set `events_logger = "none"` in `~/.config/containers/containers.conf`, but then you won't be able to use `podman container logs`, which is a big downside.
- Even if you set a default network in `~/.config/containers/containers.conf`, [Podman will ignore it](https://github.com/containers/podman/issues/25377). - ~~Even if you set a default network in `~/.config/containers/containers.conf`, [Podman will ignore it](https://github.com/containers/podman/issues/25377).~~ The documentation was not clear, you can actually set a default network in `~/.config/containers/containers.conf` using the `netns` option.
I ended up with the following configuration in `~/.config/containers/containers.conf` to workaround the issues: I ended up with the following configuration in `~/.config/containers/containers.conf` to workaround the issues:
@ -308,8 +308,11 @@ events_logfile_path="/home/edu4rdshl/.local/share/containers/containers.log"
events_logger = "file" events_logger = "file"
events_logfile_max_size = "1m" events_logfile_max_size = "1m"
[network] [containers]
default_network = "podman" # https://github.com/containers/podman/issues/25377 default_sysctls = [
"net.ipv4.ping_group_range=0 10000",
]
netns = "podman_rootless" # The default network that you want to use for containers, can be overriden with --network
``` ```
# Tips # Tips