Hi there,
I got in running without facing the message again. Issue was propably related to my own sip.service file (not noted before that exists in SIP folder a template for that)...However issue running sip.py in a container is still there...obvouisly, the changes that causing the applicable scripts to restart sip cannot handle docker environment...my dockerfile maps the internally (by SIP) used port to an external one -p 9300:80....the SIP is, thus, reachable from the host by <ip-of-host>:9300...
I am guessing that's maybe an issue, but for sure I am not an export on this...
...BTW: installed the relay 16 plugin...activiation failed with message (see above) ...restart of container brought the plugin up...tried to limit the amount of relais...than I faced in internal server error...I am really kneen to get to known...how a restart is forced based on which parameters...
I got in running without facing the message again. Issue was propably related to my own sip.service file (not noted before that exists in SIP folder a template for that)...However issue running sip.py in a container is still there...obvouisly, the changes that causing the applicable scripts to restart sip cannot handle docker environment...my dockerfile maps the internally (by SIP) used port to an external one -p 9300:80....the SIP is, thus, reachable from the host by <ip-of-host>:9300...
I am guessing that's maybe an issue, but for sure I am not an export on this...
...BTW: installed the relay 16 plugin...activiation failed with message (see above) ...restart of container brought the plugin up...tried to limit the amount of relais...than I faced in internal server error...I am really kneen to get to known...how a restart is forced based on which parameters...