I had a container with a couple of ports being used (2468 and 7474) which I deleted to create a new container with a different release, but synology/docker won’t release the ports for me to use with any other containers now. I’ve tried rebooting but that didn’t help
I tried killing the service using the port by running sudo -i netstat -nlp | grep 2468 then kill -9 <pid>.
I ran netstat to verify the ports weren’t there but it still won’t let me create it.
Error response from daemon: driver failed programming external connectivity on endpoint (8e881fe60444fc3e8db4571339d17050424ca3ef568a3209f5da17816a15285f): Bind for 0.0.0.0:2468 failed: port is already allocated
This problem might indeed happen on Synology boxes with old buggy kernels. https://bcdonadio.com/2017/when-the-blue-whale-sinks/ was a huge discussion in Synology forums years ago - I am surprised if this still is a thing with more recent kernels. I know that people reported that restarting the nas, or even restarting the Docker package (the predecessor of the Container Manager package) “solved” the issue
Anyhow, the docker version that Synology ships with its Container Manger is not vanila Docker, it is customized, maintained and supported by Synology. Even though Synology claims that Docker is the developer… it is not true for any of the customizations Synology did, to make it work with the modified Syno kernels and libraries, or the extra features that are unique to Synology.
There is nothing we (as this community forum), or Docker Inc. (as the company that maintains and supports vanilla Docker) can do here.