I have setup Docker container for access my machine docker container to another machine in local.

Create a container below command:

   		docker run -it -d --name containerName -h www.myhost.net -v /var/www/html -p 7000:8000 --net mynetwork --ip 172.11.0.10 --privileged myimagename bash

After Create A Container Details:
 


            CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS                    NAMES

            1e1e5e9b74b4        myimgaename         &quot;bash&quot;              21 minutes ago      Up 6 minutes        0.0.0.0:7000-&gt;8000/tcp   containername

NetWork Details:


		 &quot;NetworkSettings&quot;: {
            &quot;Bridge&quot;: &quot;&quot;,
            &quot;SandboxID&quot;: &quot;fe357c54c816fff0f9d642037dc9a173be7f7e42a80776d006572f6a1395969e&quot;,
            &quot;HairpinMode&quot;: false,
            &quot;LinkLocalIPv6Address&quot;: &quot;&quot;,
            &quot;LinkLocalIPv6PrefixLen&quot;: 0,
            &quot;Ports&quot;: {
                &quot;8000/tcp&quot;: [
                    {
                        &quot;HostIp&quot;: &quot;0.0.0.0&quot;,
                        &quot;HostPort&quot;: &quot;7000&quot;
                    }
                ]
            }

if I access docker  ipaddr(172.11.0.10) or hostname(www.myhost.net) in mymachine(hostmachine) it working  

But if I access with **Port** doesn&#39;t work: hostmachine ip: 192.168.1.1

      go to the browser  192.168.1.1:7000  hostmachine and locally connected anoter machine also.

But My 7000 port are listen in hostmachine:      


            # ps aux | grep 7000
			root     10437  0.0  0.2 194792 24572 pts/0    Sl+  12:33   0:00 docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 7000 -container-ip 172.11.0.10 -container-port 8000
			root     10941  0.0  0.0 118492  2324 pts/3    R+   12:44   0:00 grep --color=auto 7000


**update 1:**

          $ docker version
			Client:
			 Version:      1.11.2
			 API version:  1.23
			 Go version:   go1.5.4
			 Git commit:   b9f10c9
			 Built:        Wed Jun  1 21:39:21 2016
			 OS/Arch:      linux/amd64

			Server:
			 Version:      1.11.2
			 API version:  1.23
			 Go version:   go1.5.4
			 Git commit:   b9f10c9
			 Built:        Wed Jun  1 21:39:21 2016
			 OS/Arch:      linux/amd64



Suggest me Why Cannot access my Container to another machine. How to Resolve this Problem


Docker port forwarding not working

I can&#39;t kill or stop any docker container. I&#39;ve allowed non-privileged users to run Docker commands. And `docker run hello-world` works fine.
But I can&#39;t stop any other container.

I got following:

    $ docker stop 59e3b815d1dc
    Error response from daemon: cannot stop container: 59e3b815d1dc: 
    Cannot kill container 59e3b815d1dcf2d8c8bcd3dd641c3c033b83ac68ea2f0257a32a76468af7374c: 
    unknown error after kill: docker-runc did not terminate sucessfully: 
    container_linux.go:393: signaling init process caused &quot;permission denied&quot;
    : unknown

The same error with sudo. Meanwhile, all containers run successfully, but to stop them is possible only a full reboot of the system. 

Docker compose example:
    # Use postgres/example user/password credentials
    version: &#39;3.1&#39;
    
    services:
    
      db:
        image: postgres
        restart: always
        environment:
          POSTGRES_PASSWORD: example
    
      adminer:
        image: adminer
        restart: always
        ports:
          - 8080:8080

Docker info:

    $ docker info
    Containers: 7
     Running: 2
     Paused: 0
     Stopped: 5
    Images: 10
    Server Version: 17.12.1-ce
    Storage Driver: overlay2
     Backing Filesystem: extfs
     Supports d_type: true
     Native Overlay Diff: true
    Logging Driver: json-file
    Cgroup Driver: cgroupfs
    Plugins:
     Volume: local
     Network: bridge host macvlan null overlay
     Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
    Swarm: inactive
    Runtimes: runc
    Default Runtime: runc
    Init Binary: docker-init
    containerd version: 9b55aab90508bd389d7654c4baf173a981477d55
    runc version: 9f9c96235cc97674e935002fc3d78361b696a69e
    init version: 949e6fa
    Security Options:
     apparmor
     seccomp
      Profile: default
    Kernel Version: 4.4.0-116-generic
    Operating System: Ubuntu 16.04.4 LTS
    OSType: linux
    Architecture: x86_64
    CPUs: 4
    Total Memory: 11.61GiB
    Name: peter-pen
    ID: P6FS:C76H:WIAO:LCWC:TCHT:JEYB:6W3M:HXYD:S4E2:KTUZ:2T3Q:3GPI
    Docker Root Dir: /var/lib/docker
    Debug Mode (client): false
    Debug Mode (server): false
    Registry: https://index.docker.io/v1/
    Labels:
    Experimental: false
    Insecure Registries:
     127.0.0.0/8
    Live Restore Enabled: false
    
    WARNING: No swap limit support



docker on ubuntu 16.04 error when killing container

When using Docker, we start with a base image. We boot it up, create changes and those changes are saved in layers forming another image.

So eventually I have an image for my PostgreSQL instance and an image for my web application, changes to which keep on being persisted.

What is a container?



What is the difference between a Docker image and a container?

How do people deal with persistent storage for your Docker containers?

I am currently using this approach: build the image, e.g. for PostgreSQL, and then start the container with

    docker run --volumes-from c0dbc34fd631 -d app_name/postgres

IMHO, that has the drawback, that I must not ever (by accident) delete container &quot;c0dbc34fd631&quot;.

Another idea would be to mount host volumes &quot;-v&quot; into the container, however, the **userid** within the container does not necessarily match the **userid** from the host, and then permissions might be messed up.

Note: Instead of `--volumes-from &#39;cryptic_id&#39;` you can also use `--volumes-from my-data-container` where `my-data-container` is a name you assigned to a data-only container, e.g. `docker run --name my-data-container ...` (see the accepted answer)


How to deal with persistent storage (e.g. databases) in Docker

I&#39;ve seen a bunch of tutorials that seem do the same thing I&#39;m trying to do, but for some reason my Docker containers exit. Basically, I&#39;m setting up a web-server and a few daemons inside a Docker container. I do the final parts of this through a bash script called `run-all.sh` that I run through CMD in my Dockerfile. `run-all.sh` looks like this:

    service supervisor start
    service nginx start

And I start it inside of my Dockerfile as follows:

    CMD [&quot;sh&quot;, &quot;/root/credentialize_and_run.sh&quot;]

I can see that the services all start up correctly when I run things manually (i.e. getting on to the image with -i -t /bin/bash), and everything looks like it runs correctly when I run the image, but it exits once it finishes starting up my processes. I&#39;d like the processes to run indefinitely, and as far as I understand, the container has to keep running for this to happen. Nevertheless, when I run `docker ps -a`, I see:

    ➜  docker_test  docker ps -a
    CONTAINER ID        IMAGE                            COMMAND                CREATED             STATUS                      PORTS               NAMES
    c7706edc4189        some_name/some_repo:blah   &quot;sh /root/run-all.sh   8 minutes ago       Exited (0) 8 minutes ago                        grave_jones

What gives? Why is it exiting? I know I could just put a while loop at the end of my bash script to keep it up, but what&#39;s the right way to keep it from exiting?

How to keep Docker container running after starting services?

As the title reads, I&#39;m trying to assign more memory to my container. I&#39;m using an image from docker hub called &quot;aallam/tomcat-mysql&quot; in case that&#39;s relevant.

When I start it normally without any special flags, there&#39;s a memory limit of 2GB (even though I read that memory is unbounded if not set)

Here are my docker stats

    CONTAINER           CPU %               MEM USAGE / LIMIT       MEM %               NET I/O             BLOCK I/O           PIDS
    ba57d6c9e9d2        0.22%               145.6 MiB / 1.952 GiB   7.29%               508 B / 508 B       0 B / 6.91 MB       68

I tried setting memory explicitly like so but with same results

    docker run -d --memory=10g --memory-swap=-1 -e MYSQL_PASSWORD=password -p 3307:3306 -p 8081:8080 aallam/tomcat-mysql

I&#39;ve read that perhaps the VM is what&#39;s restricting it. But then why does docker stats show that container size limit is 2GB?


How to assign more memory to docker container

I am trying to delete a docker container by this command:

    docker rmi &lt;Image-Id&gt;
Obviously, I have replaced the Image-Id by the Id I get using:

    docker images

But I see the error below:

    Error response from daemon: conflict: unable to delete &lt;Image-ID&gt; (must be forced) - image is being used by stopped container xxxxxxxxxxx



image is being used by stopped container

I am trying Docker for the first time and do not yet have a &quot;mental model&quot;. Total beginner.

All the examples that I am looking at have included the `--rm` flag to run, such as 


```
docker run -it --rm ...
docker container run -it --rm ...
```

**Question:** 

Why do these commands include the `--rm` flag? I would think that if I were to go through the trouble of setting up or downloading a container with the good stuff in it, why remove it? I want to keep it to use again.  

So, I know I have the wrong idea of Docker.


What is the &#39;--rm&#39; flag doing?

I&#39;m completely a newbie to docker. I tried to start a exited container like follows, 

1. I listed down all available containers using `docker ps -a`. It listed the following:

    [![docker list all images][1]][1]

2. I entered the following commands to start the container which is in the exited stage and enter into the terminal of that image.

    ```sh
    docker start 79b3fa70b51d
    docker exec -it 79b3fa70b51d /bin/sh
    ```

3. It is throwing the following error.

     `FATA[0000] Error response from daemon: Container 79b3fa70b51d is not running`

But when I start the container using `docker start 79b3fa70b51d`. It throws the container ID as output which is normal if it have everything work normally. I&#39;m not sure what causes this error. Any idea about the causes and suggestions about this would be greatly helpful for me. Thanks in advance.

[1]: http://i.stack.imgur.com/HbrKI.png

Docker - Container is not running

I&#39;m thinking of using Docker to build my dependencies on a Continuous Integration (CI) server, so that I don&#39;t have to install all the runtimes and libraries on the agents themselves. 

To achieve this I would need to copy the build artifacts that are built inside the container back into the host. Is that possible?


Docker: Copying files from Docker container to host

I have a docker container running jenkins. As part of the build process, I need to access a web server that is run locally on the host machine. Is there a way the host web server (which can be configured to run on a port) can be exposed to the jenkins container?

I&#39;m running docker natively on a Linux machine.

UPDATE:

In addition to @larsks answer below, to get the IP address of the Host IP from the host machine, I do the following:
   
    ip addr show docker0 | grep -Po &#39;inet \K[\d.]+&#39;

    

How to access host port from docker container

I need to start multiple containers for the same image. If i create my compose file as shown below, it works fine. 

    version: &#39;2&#39;
    
    services:
      app01:
        image: app
      app02:
        image: app
      app03:
        image: app
      app04:
        image: app
      app05:
        image: app	

Is there any easy way for me to mention the number of instances for the compose instead of copy and pasting multiple times?


docker-compose creating multiple instances for the same image

I am trying to build a backup and restore solution for the Docker containers that we work with.

I have Docker base image that I have created, `ubuntu:base`, and do not want have to rebuild it each time with a Docker file to add files to it.

I want to create a script that runs from the host machine and creates a new container using the `ubuntu:base` Docker image and then copies files into that container.

How can I copy files from the host to the container?


How to copy files from host to Docker container?

According to tutorial I read so far, use &quot;`docker run -d`&quot; will start a container from image, and the container will run in background. This is how it looks like, we can see we already have container id.

    root@docker:/home/root# docker run -d centos
    605e3928cdddb844526bab691af51d0c9262e0a1fc3d41de3f59be1a58e1bd1d

But if I ran &quot;**`docker ps`**&quot;, nothing was returned.

So I tried &quot;**`docker ps -a`**&quot;, I can see container already exited:

    root@docker:/home/root# docker ps -a
    CONTAINER ID        IMAGE                 COMMAND             CREATED             STATUS                         PORTS               NAMES
    605e3928cddd        centos:latest         &quot;/bin/bash&quot;         31 minutes ago      Exited (0) 31 minutes ago                          kickass_swartz

Anything I did wrong? How can I troubleshoot this issue?


Docker container will automatically stop after &quot;docker run -d&quot;

Suppose I have a volume and I know its name or id.

I want to determine the list of containers (their names or ids) that use the volume.

What commands can I use to retrieve this information?

I thought it can be stored in the output of `docker volume inspect &lt;id&gt;` command but it gives me nothing useful other than the mount point (`&quot;/var/lib/docker/volumes/&lt;id&gt;&quot;`).

How to determine what containers use the docker volume?

I had multiple stopped containers and images in my machine.  
I wanted to clean up and removed all containers:  
`docker ps -a` returns nothing.  
I run `docker rmi $(docker images -q)` to remove the cached images but I get:  

&gt; Error response from daemon: conflict: unable to delete ...
&gt; (must be forced) - image is referenced in multiple repositories  

What repositories is it talking about?  

Can not remove images even though no container is running

There are scope of services which defined in docker-compose.yml. These service have been started. I need to rebuild only one of these and start it without up other services.
I run the following commands:

    docker-compose up -d # run all services
    docker-compose stop nginx # stop only one. but it still running !!!
    docker-compose build --no-cache nginx 
    docker-compose up -d --no-deps # link nginx to other services

At the end i got old nginx container.
By the way docker-compose doesn&#39;t kill all running containers !

How to rebuild docker container in docker-compose.yml?

I&#39;m getting started working with Docker. I&#39;m using the WordPress base image and docker-compose.

I&#39;m trying to ssh into one of the containers to inspect the files/directories that were created during the initial build. I tried to run `docker-compose run containername ls -la`, but that didn&#39;t do anything. Even if it did, I&#39;d rather have a console where I can traverse the directory structure, rather than run a single command. What is the right way to do this with Docker?


How do I get into a Docker container&#39;s shell?

I can see that Docker takes 12GB of my filesystem:

    2.7G    /var/lib/docker/vfs/dir
    2.7G    /var/lib/docker/vfs
    2.8G    /var/lib/docker/devicemapper/mnt
    6.3G    /var/lib/docker/devicemapper/devicemapper
    9.1G    /var/lib/docker/devicemapper
    12G     /var/lib/docker

But, how do I know how this is distributed over the containers?

I tried to attach to the containers by running (the new v1.3 command)

    docker exec -it &lt;container_name&gt; bash

and then running &#39;df -h&#39; to analyze the disk usage. It seems to be working, but not with containers that use &#39;volumes-from&#39;.


For example, I use a data-only container for MongoDB, called &#39;mongo-data&#39;.

When I run `docker run -it --volumes-from mongo-data  busybox`, and then `df -h` inside the container, It says that the filesystem mounted on `/data/db` (my &#39;mongo-data&#39; data-only container) uses 11.3G, but when I do `du -h /data/db`, it says that it uses only 2.1G.

So, how do I analyze a container/volume disk usage? Or, in my case, how do I find out the &#39;mongo-data&#39; container size?

All Docker Container Solutions on Gang of Coders

Total of 19 Docker Container Solutions