the new container which created by sameersbn/squid could not be start.

[chenylon]

hi I get the sameersbn/squid ,but I need use my squid.conf file. so i do this： $ sudo docker run -i -t sameersbn/squid /bin/bash I custom the /etc/squid3/squid.conf, modify it and save it. and exit. create a new image "squid-new" . $ sudo docker commit squid-new $ docker run --name squid-d --restart=always --publish 9000:9000 squid-new in my custom squid.conf,the port is 9000. but the container is still restarting. it can't be started. why is this? so how to modify sameersbn/squid image, and let it work?

[waoywssy]

I had the same issue. The container keeps restarting, don't know why

[waoywssy]

hi I get the sameersbn/squid ,but I need use my squid.conf file. so i do this： $ sudo docker run -i -t sameersbn/squid /bin/bash I custom the /etc/squid3/squid.conf, modify it and save it. and exit. create a new image "squid-new" . $ sudo docker commit squid-new $ docker run --name squid-d --restart=always --publish 9000:9000 squid-new in my custom squid.conf,the port is 9000. but the container is still restarting. it can't be started. why is this? so how to modify sameersbn/squid image, and let it work?

I found the issue could be raised by the low memory of my VPS. The docker image works on another AWS EC2.