Running my containers works as it did in the previous version.
After update to beta18, I re-launched my containers from a script and got this error:
+ docker run -d --restart=always --net=wnet -v /Users/kdh/walri.com/pvs/certs:/certs --name proxy-mail -h proxy-mail -p 9930-9999:9930-9999 -p 465:465 -p 587:587 walr.io/mail-proxy b99fbdc78cfa5104b59ea8472f95a57f4077f3deda157106a9b9ed3f7f7adb4d docker: Error response from daemon: driver failed programming external connectivity on endpoint proxy-mail (f0830724d5513700da999f88b9b6552cf72b6099c8c302585f938d0af24be6f8): iptables failed: iptables --wait -t nat -A POSTROUTING -p tcp -s 172.18.0.24 -d 172.18.0.24 --dport 9943 -j MASQUERADE: Fatal error: exception Unix.Unix_error(Unix.ENOTCONN, "open", "/var/log/service-port-opener.log") (exit status 2).
I stopped/removed all containers and reran my startup script and the above container worked but the next container started in the script failed to launch:
+ docker run -d --restart=always --net=wnet -v /Users/kdh/walri.com/pvs/certs:/certs --name proxy-wmail -h proxy-wmail -p 2587:587 walr.io/wmail-proxy cf097a89a90be634622d7cbce2b59f220f0fd2be95cde9367a059e5f8f9b240c docker: Error response from daemon: driver failed programming external connectivity on endpoint proxy-wmail (a03ff1d4df8be9a681dcb19553bd513f9c6f1075760df42b07359f8ffd8368ce): Bind for 0.0.0.0:2587 failed: port is already allocated.
I then restarted Docker and reran my script but failed on the same proxy-wmail container run with the same error. So, I ‘reset’ Docker (through the Preferences pane) which apparently re-installs Docker on my Mac, rebuilt my images and executed my startup script. Now, the script runs to completion and all containers are running.
Version 1.12.0-rc3-beta18 (build: 9969)
Steps to reproduce the behavior
Not really reproducible as the first iptables error did not re-occur on the subsequent rerun. The second error about the host port already being allocated was reproducible (on 2 runs), but went away with the full reset of docker. When I did the initial upgrade to beta18, all containers were running before upgrading, but after the beta upgrade, all containers were stopped so I removed them and ran my startup script (which resulted in the initial iptables error above).
Full Reset resulted in success.