Replies: 1 comment
|
Hi @miloit, To answer your questions:
services:
otbr:
image: openthread/border-router:latest
container_name: otbr
restart: unless-stopped
privileged: true
network_mode: host
environment:
- OT_RCP_DEVICE=spinel+hdlc+uart:///dev/serial/by-id/usb-dresden_elektronik_Thread_RCP__ConBee_II__DE2665925-if00?uart-baudrate=115200
- OT_INFRA_IF=eth0
- OT_THREAD_IF=wpan0
- OT_WEB_LISTEN_ADDR=0.0.0.0
- OT_WEB_LISTEN_PORT=80
- OT_REST_LISTEN_ADDR=0.0.0.0
- OT_REST_LISTEN_PORT=8081
volumes:
- /dev:/dev |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Description
When attempting to configure OTBR port bindings via docker-compose entrypoint with sed commands, the container enters a restart loop. The sed modifications should happen before services start, but instead fail and setup-host loops infinitely.
Environment
Reproduction Steps
docker-compose.yml:
Result:
(setup-host loops indefinitely)
Expected Behavior
Current Workaround
Using docker exec after container start works perfectly:
Questions
/etc/default/otbr-webnot exist when entrypoint runs?Additional Context
All reactions