matterbridge
Version:
Matterbridge plugin manager for Matter
117 lines (82 loc) • 4.55 kB
Markdown
<!-- eslint-disable markdown/no-multiple-h1 -->
# <img src="https://matterbridge.io/assets/matterbridge.svg" alt="Matterbridge Logo" width="64px" height="64px"> Matterbridge Podman configuration
[](https://www.npmjs.com/package/matterbridge)
[](https://www.npmjs.com/package/matterbridge)
[](https://hub.docker.com/r/luligu/matterbridge)
[](https://hub.docker.com/r/luligu/matterbridge)


[](https://codecov.io/gh/Luligu/matterbridge)
[](https://prettier.io/)
[](https://eslint.org/)
[](https://www.typescriptlang.org/)
[](https://nodejs.org/)
[](https://matterbridge.io)
[](https://www.npmjs.com/package/matter-history)
[](https://www.npmjs.com/package/node-ansi-logger)
[](https://www.npmjs.com/package/node-persist-manager)
---
# Production configuration
## Install Podman if it is not already installed
```bash
cd ~
sudo apt update
sudo apt install podman -y
podman --version
```
## Run matterbridge with podman
The 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.
### First create the Matterbridge directories
This will create the required directories if they don't exist
```bash
cd ~
mkdir -p ./Matterbridge
mkdir -p ./.matterbridge
sudo chown -R $USER:$USER ./Matterbridge ./.matterbridge
```
You 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).
### Run the Podman container (root mode) and start it
The container must have full access to the host network (needed for matter mdns).
```bash
podman run --name matterbridge \
-v ~/Matterbridge:/root/Matterbridge \
-v ~/.matterbridge:/root/.matterbridge \
--network host --restart always -d docker.io/luligu/matterbridge:latest
```
You 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.
### Integrate the mattebridge podman container with systemd for automatic startup after reboots
```bash
podman generate systemd --name matterbridge --files --new
sudo mv container-matterbridge.service /etc/systemd/system/
sudo systemctl enable container-matterbridge
sudo systemctl start container-matterbridge
```
### Start the Podman container
```bash
podman start matterbridge
```
### Stop the Podman container
```bash
podman stop matterbridge
```
### Restart the Podman container
```bash
podman restart matterbridge
```
### Remove the Podman container
```bash
podman rm matterbridge
```
### Shows the logs
```bash
podman logs matterbridge
```
### Shows the logs real time (tail)
```bash
podman logs --tail 1000 -f matterbridge
```