cannot set multiple networks without bridge network mode

[denics]

when laucnching podman-compose --project-name ovos --file docker-compose.yml up --detach I have this error

['podman', '--version', '']
using podman version: 4.3.1
** excluding:  set()
['podman', 'network', 'exists', 'ovos_default']
podman run --name=ovos_messagebus -d --security-opt label=disable --label io.podman.compose.config-hash=123 --label io.podman.compose.project=ovos --label io.podman.compose.version=0.0.1 --label com.docker.compose.project=ovos --label com.docker.compose.project.working_dir=/home/denix/Git/ovos/ovos-docker/compose --label com.docker.compose.project.config_files=docker-compose.yml --label com.docker.compose.container-number=1 --label com.docker.compose.service=ovos_messagebus --network host -e TZ=Europe/Paris -v /home/denix/Git/ovos/docker/ovos/config:/home/ovos/.config/mycroft:ro -v /home/denix/Git/ovos/docker/ovos/tmp:/tmp/mycroft --net ovos_default --network-alias ovos_messagebus --log-driver=json-file --log-opt=mode=non-blocking --log-opt=max-buffer-size=4m --log-opt=max-size=200m --log-opt=max-file=1 --hostname ovos_messagebus --pull always --restart unless-stopped docker.io/smartgic/ovos-messagebus:alpha
Error: cannot set multiple networks without bridge network mode, selected mode host: invalid argument
exit code: 125
podman start ovos_messagebus
Error: no container with name or ID "ovos_messagebus" found: no such container

I found a mention of this error on the podman issues list: https://github.com/containers/podman/issues/13109

[goldyfruit]

Did you try with the latest version of Podman and slirp4netns?

[denics]

Podman on Debian 12 and did not modify your scripts yet

[goldyfruit]

On Debian 11/12, I'm always using this Kubic project to get the latest version of podman, containerd, slirp4netns, etc...

https://podman.io/docs/installation#installing-on-linux

[goldyfruit]

@denics any update on this?

[goldyfruit]

Just tested successfully on Debian Bookworm (12) with podman-compose version: 1.0.6 and podman version: 4.5.1.

[denics]

I rather prefer to use standard packages on my side

[goldyfruit]

I rather prefer to use standard packages on my side

Then I guess you will have to wait until Debian ports a newer Podman version (and package dependencies) into stable .

Just in case you change your mind about using a more updated version of Podman.

sudo mkdir -p /etc/apt/keyrings
curl -fsSL "https://download.opensuse.org/repositories/devel:/kubic:/libcontainers:/unstable/Debian_Testing/Release.key" | gpg --dearmor | sudo tee /etc/apt/keyrings/devel_kubic_libcontainers_unstable.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/devel_kubic_libcontainers_unstable.gpg] https://download.opensuse.org/repositories/devel:kubic:libcontainers:unstable/Debian_Testing/ /" | sudo tee /etc/apt/sources.list.d/devel:kubic:libcontainers:unstable.list
sudo apt update
sudo apt install podman python3-pip libyajl2 libslirp0 
pip3 install podman-compose --break-system-packages