fix: podman integration

This commit is contained in:
Clément Désiles
2026-05-29 21:24:58 +02:00
parent 305b8324db
commit 1d00432061
9 changed files with 42 additions and 9 deletions
+5
View File
@@ -18,3 +18,8 @@ podman_log_driver: journald
# k8s-file driver settings (only used when podman_log_driver: k8s-file)
podman_log_max_size: 10mb # Max size per log file before rotation
podman_log_max_files: 5 # Max number of rotated log files to keep
# Host gateway address exposed inside rootless containers (pasta --map-host-loopback)
# Containers can connect to this address to reach services bound to host loopback.
# Pasta translates the destination to 127.0.0.1 on the host side.
podman_gw_gateway: 100.64.0.1
+8 -1
View File
@@ -29,5 +29,12 @@ runtime = "{{ podman_runtime }}"
network_backend = "netavark"
[network]
# Default rootless network command (pasta for better performance)
# Default rootless network command (pasta for better performance).
# Note: default_rootless_network_cmd only accepts the mode name ("pasta" or
# "slirp4netns"). Extra pasta arguments must be set via pasta_options below;
# the "pasta:--arg=value" syntax is only valid for the CLI --network= flag.
default_rootless_network_cmd = "pasta"
# --map-host-loopback exposes the host's loopback to containers via {{ podman_gw_gateway }}.
# Containers connecting to {{ podman_gw_gateway }} reach host services bound to 127.0.0.1.
pasta_options = ["--map-host-loopback", "{{ podman_gw_gateway }}"]