System Info:
Debian Bookworm (12)
Kernel: 6.1.0-44-amd64
Docker version 29.3.0, build 5927d80
The volume mounts overwrite the internal /etc/freeswitch diretory which results in the service being unable to start.
Logs:
freeswitch | ERROR: Failed to set SCHED_FIFO scheduler (Function not implemented)
freeswitch | ERROR: Failed to set SCHED_OTHER scheduler (Function not implemented)
freeswitch | 2026-03-18 11:06:01.081887 0.00% [INFO] switch_event.c:714 Activate Eventing Engine.
freeswitch | Cannot Initialize [Cannot Open log directory or XML Root!]
freeswitch | 2026-03-18 11:06:01.092394 0.00% [WARNING] switch_event.c:685 Create additional event dispatch thread 0
freeswitch | 2026-03-18 11:06:01.092476 0.00% [ERR] switch_xml.c:1439 Couldn't open /etc/freeswitch/freeswitch.xml (No such file or directory)
freeswitch exited with code 255 (restarting)
freeswitch | ERROR: Failed to set SCHED_FIFO scheduler (Function not implemented)
freeswitch | ERROR: Failed to set SCHED_OTHER scheduler (Function not implemented)
freeswitch | 2026-03-18 11:06:01.652548 0.00% [INFO] switch_event.c:714 Activate Eventing Engine.
freeswitch | Cannot Initialize [Cannot Open log directory or XML Root!]
freeswitch | 2026-03-18 11:06:01.663068 0.00% [WARNING] switch_event.c:685 Create additional event dispatch thread 0
freeswitch | 2026-03-18 11:06:01.663139 0.00% [ERR] switch_xml.c:1439 Couldn't open /etc/freeswitch/freeswitch.xml (No such file or directory)
It works if I exclude the mounts, at which point the default configuration is created by freeswitch.
I'm note sure what the best way is to get around this, maybe an init container, that ensures the default configuration gets created? Otherwise one could run the container, copy the generated default config to the host system and then mount these files into the container.
Will let you know if I find a way to solve!
Kind Regards.
System Info:
Debian Bookworm (12)
Kernel: 6.1.0-44-amd64
Docker version 29.3.0, build 5927d80
The volume mounts overwrite the internal /etc/freeswitch diretory which results in the service being unable to start.
Logs:
It works if I exclude the mounts, at which point the default configuration is created by freeswitch.
I'm note sure what the best way is to get around this, maybe an init container, that ensures the default configuration gets created? Otherwise one could run the container, copy the generated default config to the host system and then mount these files into the container.
Will let you know if I find a way to solve!
Kind Regards.