PROBLEM Talking to some developers at #docker@freenode, the problem was clear to everyone: DNS and the environment. The build works just fine at a regular Internet connection at home. SOLUTION: This problem occurs in an environment that has a private DNS server, or the network blocks the Google’s DNS servers. Even if the docker container … Read more
The network stack, as in “the code”, is definitely not in the container, it’s in the kernel of which there’s only one shared by the host and all containers (you already knew this). What each container has is its own separate network namespace, which means it has its own network interfaces and routing tables. Here’s … Read more
The –ipc=host and –ipc=container:id options have since been added to the Docker create and run commands to share IPC resources. –ipc=”” : Set the IPC mode for the container, ‘container:<name|id>’: reuses another container’s IPC namespace ‘host’: use the host’s IPC namespace inside the container IPC with the host docker run –ipc=host <image> IPC with another … Read more
Posted by one friend in comments Hi Slava, sorry that your question was closed. For the record, Slava is talking about docker.io, a runtime for linux containers. Yes, docker export is a suitable approach. It will generate a tarball of your entire container filesystem state, and dump it on stdout. So docker export $CONTAINER_ID > … Read more
You have stages called base, build, and debug. Then in the final stage you have: COPY –from=publish/app /app . When docker can’t find the stage with that name, publish/app, it tries to find that image, which doesn’t exist. I’m guessing you want to copy from the build stage, e.g. COPY –from=build /app .
Docker shares resources at kernel level. This means application logic is in never replicated when it is ran. If you start notepad 1000 times it is still stored only once on your hard disk, the same counts for docker instances. If you run 100 instances of the same docker image, all you really do is … Read more
You can connect to your mysql container and run your commands using: docker exec -it mysql bash -l (Where mysql is the name you gave the container) Keep in mind that anything you do will not persist to the next time your run a container from the same image.
If you want to include a /new/path in the Dockerfile, adding the line: ENV PATH “$PATH:/new/path” in Dockerfile should work.
if I want to revert the container I can try to commit an image, and then later delete the container, and create a new container from the committed image. But if I do that the volume gets deleted and all my data is gone As the docker user guide explains, data volumes are meant to … Read more
Just got it. As regan pointed out, I had to add the user to the sudoers group. But the main reason was I’d forgotten to update the repositories cache, so apt-get couldn’t find the sudo package. It’s working now. Here’s the completed code: FROM ubuntu:12.04 RUN apt-get update && \ apt-get -y install sudo RUN … Read more