cd ~
sudo apt update
sudo apt install podman -y
podman --versionThe Matterbridge Docker image, which includes a manifest list for the linux/amd64, linux/arm64 and linux/arm/v7 architectures, is published on Docker Hub and can be used with podman.
Podman handles container restarts a little differently than Docker. The --restart always flag doesn’t work exactly the same. If you want the container to automatically restart when the system reboots or if it crashes, you can create a systemd unit for the Podman container.
This will create the required directories if they don't exist
cd ~
mkdir -p ./Matterbridge
mkdir -p ./.matterbridge
sudo chown -R $USER:$USER ./Matterbridge ./.matterbridgeYou may need to adapt the script to your setup:
- ./Matterbridge is the position outside of the container of your matterbridge plugin directory (inside your home directory).
- ./.matterbridge is the position outside of the container of your matterbridge storage directory (inside your home directory).
The container must have full access to the host network (needed for matter mdns).
podman run --name matterbridge \
-v ~/Matterbridge:/root/Matterbridge \
-v ~/.matterbridge:/root/.matterbridge \
--network host --restart always --stop-timeout 60 -d docker.io/luligu/matterbridge:latestYou may need to adapt the script to your setup:
- ~/Matterbridge is the position outside of the container of your matterbridge plugin directory.
- ~/.matterbridge is the position outside of the container of your matterbridge storage directory.
podman generate systemd --name matterbridge --files --new
sudo mv container-matterbridge.service /etc/systemd/system/
sudo systemctl enable container-matterbridge
sudo systemctl start container-matterbridgepodman start matterbridgepodman stop matterbridgepodman restart matterbridgepodman rm matterbridgepodman logs matterbridgepodman logs --tail 1000 -f matterbridge