nsenter

Background I had build a npm server(sinopia) docker image( https://github.com/feuyeux/docker-atue/blob/master/docker-images/feuyeux_sinopia.md ), and in the CMD line, it will run the start.sh every time when the container is generated. CMD ["/opt/sinopia/start.sh"] This shell will create a yaml file dynamically. sed -e 's/\#listen\: localhost/listen\: 0.0.0.0/' -e 's/allow_publish\: admin/allow_publish\: all/' /tmp/config.yaml > /opt/sinopia/config.yaml Question I wish I could edit this config.yaml when the container is running, because I hope the content should be changed on demand. see the

I've been using nsenter for the last few months to get a shell running on a container for debugging purposes. I have heard about and used docker exec which was introduced in version 1.3. Docker exec seems to be the new best practice for the purpose of getting inside a container for debugging purposes, but I'm wondering if there are any drawbacks to using docker exec versus nsenter. Information comparing the two is scant. Are there any specific problems I should watch out for or avoid when using docker exec versus nsenter? That is not entirely clear right now. But I would support the view that