Error installing modbus-proxy on Synology with docker compose file

[redi78]

• ModBus TCP proxy version: latest
• Python version:
• Operating System: Synology DSM 7.2

Description

I want to install modbus-proxy on my Synology NAS via Docker compose File.

`version: "3" services: modbus-proxy: security_opt:

• seccomp=unconfined container_name: modbus-proxy image: tiagocoutinho/modbus-proxy:latest ports:
  • "5020:502" environment:
• RUST_BACKTRACE=full volumes:
• /volume2/docker/modbus_proxy/config.yml:/etc/modbus-proxy.yml restart: always`

Error Message:

Container will not start and i get following error message:

thread 'main' panicked at 'calledResult::unwrap()on anErrvalue: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }', /modbus-proxy-rs/src/lib.rs:181:67

Could someone help please?

Thank you :-)

[etofi]

I use it on my 218+ with this create statement.

docker create \
--name=ModbusTCP_Proxy \
--net=macvlan \
--ip 192.168.178.169 \
--restart unless-stopped \
-e TZ=Europe/Berlin \
-v /volume1/docker/ModbusTCP_Proxy/modbus-proxy.yml:/etc/modbus-proxy.yml \
tiagocoutinho/modbus-proxy:latest

[giss69]

I use it on my 218+ with this create statement.

docker create \
--name=ModbusTCP_Proxy \
--net=macvlan \
--ip 192.168.178.169 \
--restart unless-stopped \
-e TZ=Europe/Berlin \
-v /volume1/docker/ModbusTCP_Proxy/modbus-proxy.yml:/etc/modbus-proxy.yml \
tiagocoutinho/modbus-proxy:latest

Can you please share your modbus-proxy.yml? ip 192.168.178.169 which ip is it? (container ip?) Thank you!

[giss69]

@redi78 I've same issue. Did you solve this problem?

[giss69]

but this build: https://github.com/Akulatraxas/ha-modbusproxy/ (This addon uses the modbus-proxy of tiagocoutinho:) is working on Synology but only via HA. Why is original not working?

[etofi]

I use it on my 218+ with this create statement.

docker create \
--name=ModbusTCP_Proxy \
--net=macvlan \
--ip 192.168.178.169 \
--restart unless-stopped \
-e TZ=Europe/Berlin \
-v /volume1/docker/ModbusTCP_Proxy/modbus-proxy.yml:/etc/modbus-proxy.yml \
tiagocoutinho/modbus-proxy:latest

Can you please share your modbus-proxy.yml? ip 192.168.178.169 which ip is it? (container ip?) Thank you!

The IP is the macvlan IP of the modbus proxy container.

devices:
- modbus:
    url: 192.168.178.50:502
  listen:
    bind: 0:9000
- modbus:
    url: 192.168.178.106:502
  listen:
    bind: 0:9001

[giss69]

Thank you! now the error has gone! but a don't receive any data from invertor. devices:

• modbus: url: 192.168.30.53:502 (my invertor) listen: bind: 0:9001 Docker running on 192.168.10.5. I'm trying to get data via modus-proxy container with address : 192.168.10.5:9001 Port maping: host:9001, container:502 what is wrong?

[etofi]

Thank you! now the error has gone! but a don't receive any data from invertor. devices:

* modbus:
  url: 192.168.30.53:502 (my invertor)
  listen:
  bind: 0:9001
  Docker running on 192.168.10.5. I'm trying to get data via modus-proxy container with address : 192.168.10.5:9001
  Port maping: host:9001, container:502
  what is wrong?

Unfortunately, I don't know. I can only say that I often had problems accessing services when I used the network mode bridge. That's why I give all important services their own IP address via macvlan - so there are no problems with access or TCP ports. Maybe you can try it with that.

Range 192.168.178.161 - 192.168.178.190 
docker network create -d macvlan -o parent=eth0 --subnet=192.168.178.0/24 --gateway=192.168.178.1 --ip-range=192.168.178.160/27 --aux-address 'host=192.168.178.191' macvlan

[giss69]

I tried it with macvlan too. The same no data.