Yes, use the name of the service:

    docker-compose build elasticsearch

    docker-compose up -d --no-deps --build &lt;service_name&gt;

[Source](https://staxmanade.com/2016/09/how-to-update-a-single-running-docker-compose-container/)

if you want to **run** and **recreate** a specific service inside your docker-compose file you can do it the same way as @dnephin proposed, like

    $ docker-compose up -d --force-recreate --no-deps --build service_name

Suppose your docker-compose.yml file is like

    version: &#39;3&#39;
    services:
      service_1:
          .....
      service_2:
          .....

You could added `--no-start` flag to docker-compose, and start later since you will only build one service.

There is some webpack dev server config (it&#39;s part of the whole config):

    config.devServer = {
      contentBase: &#39;./&#39; + (options.publicFolder ? options.publicFolder : &#39;public&#39;),
      stats: {
        modules: false,
        cached: false,
        colors: true,
        chunk: false
      },
      proxy: [{
        path: /^\/api\/(.*)/,
        target: options.proxyApiTarget,
        rewrite: rewriteUrl(&#39;/$1&#39;),
        changeOrigin: true
      }]
    };
  
    function rewriteUrl(replacePath) {
      return function (req, opt) {  // gets called with request and proxy object
        var queryIndex = req.url.indexOf(&#39;?&#39;);
        var query = queryIndex &gt;= 0 ? req.url.substr(queryIndex) : &quot;&quot;;
        req.url = req.path.replace(opt.path, replacePath) + query;
        console.log(&quot;rewriting &quot;, req.originalUrl, req.url);
      };
    }

I execute webpack with the following command:

    node node_modules/webpack-dev-server/bin/webpack-dev-server.js --host 0.0.0.0 --history-api-fallback --debug --inline --progress --config config/webpack.app.dev.js

I can get access to dev server using `http://localhost:8080` on my local machine, but I also want to get access to my server from my mobile, tablet (they are in the same Wi-Fi network).

How can I enable it? Thanks!

How to get access to webpack-dev-server from devices in local network?

I&#39;d like to be able to await on an observable, e.g.

    const source = Rx.Observable.create(/* ... */)
    //...
    await source;


A naive attempt results in the await resolving immediately and not blocking execution

Edit:
The pseudocode for my full intended use case is:

    if (condition) {
      await observable;
    }
    // a bunch of other code

I understand that I can move the other code into another separate function and pass it into the subscribe callback, but I&#39;m hoping to be able to avoid that.

How can I `await` on an Rx Observable?

Using Compose, if I run `docker-compose build`, it will rebuild **all** the containers :

    &gt; docker-compose build
    Building elasticsearch
    Step 1 : FROM elasticsearch:2.1
     ---&gt; a05cc7ed3f32
    Step 2 : RUN /usr/share/elasticsearch/bin/plugin install analysis-phonetic
     ---&gt; Using cache
     ---&gt; ec07bbdb8a18
    Successfully built ec07bbdb8a18
    Building search
    Step 1 : FROM php:5.5.28-fpm
     ---&gt; fcd24d1058c0
    ...

Even when rebuilding using cache, this takes time. So my question is: 

Is there a way to **rebuild only one specific container?**

docker compose build single container

Using Compose, if I run <code>docker-compose build</code>, it will rebuild all the containers :
<pre><code class="hljs language-sql">> docker-compose build
Building elasticsearch
Step 1 : FROM elasticsearch:2.1
 ---> a05cc7ed3f32
Step 2 : RUN /usr/share/elasticsearch/bin/plugin install analysis-phonetic
 ---> Using cache
 ---> ec07bbdb8a18
Successfully built ec07bbdb8a18
Building search
Step 1 : FROM php:5.5.28-fpm
 ---> fcd24d1058c0
...
</code></pre>
Even when rebuilding using cache, this takes time. So my question is:
Is there a way to rebuild only one specific container?

In docker, files created inside containers tend to have unpredictable ownership while inspecting them from the host. The owner of the files on a volume is root (uid 0) by default, but as soon as non-root user accounts are involved in the container and writing to the file system, owners become more or less random from the host perspective.

It is a problem when you need to access volume data from the host using the same user account which is calling the docker commands. 

Typical workarounds are 

  - forcing users uIDs at creation time in Dockerfiles (non portable) 
  - passing the UID of the host user to the `docker run` command as an environment variable and then running some `chown` commands on the volumes in an entrypoint script. 

Both these solutions can give some control over the actual permissions outside the container.

I expected user namespaces to be the final solution to this problem. I have run some tests with the recently released version 1.10 and --userns-remap set to my desktop account. However, I am not sure that it can make file ownership on mounted volumes easier to deal with, I am afraid that it could actually be the opposite.

Suppose I start this basic container

    docker run -ti -v /data debian:jessie /bin/bash
    echo &#39;hello&#39; &gt; /data/test.txt
    exit


And then inspect the content from the host : 

    ls -lh /var/lib/docker/100000.100000/volumes/&lt;some-id&gt;/_data/

    -rw-r--r-- 1 100000 100000 6 Feb  8 19:43 test.txt


This number &#39;100000&#39; is a sub-UID of my host user, but since it does not correspond to my user&#39;s UID, I still can&#39;t edit test.txt without privileges. This sub-user does not seem to have any affinity with my actual regular user outside of docker. It&#39;s not mapped back.

The workarounds mentioned earlier in this post which consisted of aligning UIDs between the host and the container do not work anymore due to the `UID-&gt;sub-UID` mapping that occurs in the namespace.

Then, is there a way to run docker with user namespace enabled (for improved security), while still making it possible for the host user running docker to own the files generated on volumes? 

Docker and --userns-remap, how to manage volume permissions to share data between host and container?

I want to use Dockerizing MongoDB and store data in local volume.

But .. failed ...

It has `mongo:latest` images

    kerydeMacBook-Pro:~ hu$ docker images
    REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
    mongo               latest              b11eedbc330f        2 weeks ago         317.4 MB
    ubuntu              latest              6cc0fc2a5ee3        3 weeks ago         187.9 MB

I want to store the mono data in `~/data`. so ---

    kerydeMacBook-Pro:~ hu$ docker run -p 27017:27017 -v ~/data:/data/db --name mongo -d mongo
    f570073fa3104a54a54f39dbbd900a7c9f74938e2e0f3f731ec8a3140a418c43

But ... it not work...

&gt; docker ps -- no daemon mongo

 
    kerydeMacBook-Pro:~ hu$ docker ps
    CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

try to run &quot;mongo&quot; --failed

    kerydeMacBook-Pro:~ hu$ docker exec -it f57 bash
    Error response from daemon: Container f57 is not running

&gt; docker inspect mongo

    kerydeMacBook-Pro:~ hu$ docker inspect mongo
    [
    {
        &quot;Id&quot;: &quot;f570073fa3104a54a54f39dbbd900a7c9f74938e2e0f3f731ec8a3140a418c43&quot;,
        &quot;Created&quot;: &quot;2016-02-15T02:19:01.617824401Z&quot;,
        &quot;Path&quot;: &quot;/entrypoint.sh&quot;,
        &quot;Args&quot;: [
            &quot;mongod&quot;
        ],
        &quot;State&quot;: {
            &quot;Status&quot;: &quot;exited&quot;,
            &quot;Running&quot;: false,
            &quot;Paused&quot;: false,
            &quot;Restarting&quot;: false,
            &quot;OOMKilled&quot;: false,
            &quot;Dead&quot;: false,
            &quot;Pid&quot;: 0,
            &quot;ExitCode&quot;: 100,
            &quot;Error&quot;: &quot;&quot;,
            &quot;StartedAt&quot;: &quot;2016-02-15T02:19:01.74102535Z&quot;,
            &quot;FinishedAt&quot;: &quot;2016-02-15T02:19:01.806376434Z&quot;
        },
      

 

    &quot;Mounts&quot;: [
            {
                &quot;Source&quot;: &quot;/Users/hushuming/data&quot;,
                &quot;Destination&quot;: &quot;/data/db&quot;,
                &quot;Mode&quot;: &quot;&quot;,
                &quot;RW&quot;: true
            },
            {
                &quot;Name&quot;: &quot;365e687c4e42a510878179962bea3c7699b020c575812c6af5a1718eeaf7b57a&quot;,
                &quot;Source&quot;: &quot;/mnt/sda1/var/lib/docker/volumes/365e687c4e42a510878179962bea3c7699b020c575812c6af5a1718eeaf7b57a/_data&quot;,
                &quot;Destination&quot;: &quot;/data/configdb&quot;,
                &quot;Driver&quot;: &quot;local&quot;,
                &quot;Mode&quot;: &quot;&quot;,
                &quot;RW&quot;: true
            }
        ],

**If I do not set data volume, mongo image can work!** 

But, when setting data volume, it can&#39;t. Who can help me?

How to set docker mongo data volume

I set up a simple Node server in Docker.

**Dockerfile**

    FROM node:latest
    RUN apt-get -y update
    ADD example.js .
    EXPOSE 1337   
    CMD node example.js

**example.js**

&lt;!-- language: javascript --&gt;

    var http = require(&#39;http&#39;);
    http.createServer(function (req, res) {
      res.writeHead(200, {&#39;Content-Type&#39;: &#39;text/plain&#39;});
      res.end(&#39;Hello World\n&#39;+new Date);
    }).listen(1337, &#39;127.0.0.1&#39;);
    console.log(&#39;Server running at http://127.0.0.1:1337/&#39;);

Now build the image

    $ docker build -t node_server .

Now run in container

    $ docker run -p 1337:1337 -d node_server  
    $ 5909e87302ab7520884060437e19ef543ffafc568419c04630abffe6ff731f70

Verify the container is running and ports are mapped:

    $ docker ps  

    CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS                    NAMES
    5909e87302ab        node_server         &quot;/bin/sh -c &#39;node exa&quot;   7 seconds ago       Up 6 seconds        0.0.0.0:1337-&gt;1337/tcp   grave_goldberg

Now let&#39;s attach to the container and verify the server is running inside:

    $ docker exec -it 5909e87302ab7520884060437e19ef543ffafc568419c04630abffe6ff731f70 /bin/bash 

And in the container command line type:

    root@5909e87302ab:/# curl http://localhost:1337
    Hello World
    Mon Feb 15 2016 16:28:38 GMT+0000 (UTC)

Looks good right?

**The problem**

When I execute the same curl command on the host (or navigate with my browser to http://localhost:1337) I see nothing.

Any idea why the port mapping between container and host doesn&#39;t work?

Things I already tried:

 - Running with the `--expose 1337` flag

Containerized Node server inaccessible with server.listen(port, &#39;127.0.0.1&#39;)

I have unit tests running on my build server and would like to capture the log results for analysis when something fails. I have yet to find a way to redirect the output of `docker-compose logs` to a file, or to find where the log files themselves actually live.

I want the equivalent of:

    docker-compose logs &gt; logs.txt

--------

Edit - clarification:

All of my docker containers produce useful logs, which a manual run of `docker-compose logs` reveals. I want to script this process to save those same logs to a file that is an artifact on my build server. Essentially, the output of `docker-compose logs` saved to a file, however `docker-compose logs` never exits.

Save docker-compose logs to a file

I have a docker-compose yml file as in below

&lt;!-- language: lang-yml --&gt;

    version: &#39;2&#39;
    services:
      nodejs:
        build:
          context: .
          dockerfile: DockerFile
        ports:
          - &quot;4000:4000&quot;
        links:
          - redis
        expose:
          - &quot;6379&quot;
      redis:
        build:
          context: .
          dockerfile: Dockerfile-redis

My goal is to forward nodejs-127.0.0.1 port 6379 to the redis host.  I can already ping redis from the nodejs machine, but the ports are not mapped.  Tried expose options, but no chance either.

Docker compose port mapping

I have a Dockerfile where an `ARG` is used in the `CMD` instruction:

    ARG MASTER_NAME
    CMD spark-submit --deploy-mode client --master ${MASTER_URL}

The arg is passed via docker-compose:

      spark:
        build:
          context: spark
          args:
            - MASTER_URL=spark://master:7077

However, the `ARG` does not seem to get expanded for `CMD`. After I `docker-compose up`.

Here&#39;s what inspect shows:

    docker inspect  -f &quot;{{.Name}} {{.Config.Cmd}}&quot; $(docker ps -a -q)
    /spark {[/bin/sh -c spark-submit --deploy-mode client --master ${MASTER_URL}]}


Is Docker ARG allowed within CMD instruction

According to the Docker Compose&#39;s [compose-file documentation][1]:

 - `depends_on` - Express dependency between services.
 - `links` - Link to containers in another service and also **express dependency between services** in the same way as [depends_on][2].

I don&#39;t understand the purpose of linking to other containers so the difference between two options still seems quite difficult for me.

It would be much easier if there is an example, but I can&#39;t find any.

I noticed, when I link container B with container A then container B will be &quot;pingable&quot; inside container A&#39;s shell.

I ran `ping B` inside container A&#39;s `bash` and got result like this (just for reference, image from the Internet)

[![enter image description here][3]][3]

  [1]: https://docs.docker.com/compose/compose-file
  [2]: https://docs.docker.com/compose/compose-file/#depends-on
  [3]: http://i.stack.imgur.com/DI9Io.jpg

Difference between links and depends_on in docker_compose.yml

In order to keep track of the volumes used by docker-compose, I&#39;d like to use named volumes. This works great for &#39;normal&#39; volumes like

&lt;!-- language-all: lang-yaml --&gt;

    version: 2
    services: 
      example-app:
        volume:
          -named_vol:/dir/in/container/volume
    volumes:
      named_vol:

But I can&#39;t figure out how to make it work when mounting the local host.
I&#39;m looking for something like:

    version: 2
    services: 
      example-app:
        volume:
          -named_homedir:/dir/in/container/volume
    volumes:
      named_homedir: /c/Users/
 
or 

    version: 2
    services: 
      example-app:
        volume:
          -/c/Users/:/home/dir/in/container/ --name named_homedir


is this in any way possible or am I stuck with anonymous volumes for mounted ones?


Content Type	Original Author	Original Content on Stackoverflow
Question	Marc Perrin-Pelletier	View Question on Stackoverflow
Solution 1 - Docker	dnephin	View Answer on Stackoverflow
Solution 2 - Docker	FTM	View Answer on Stackoverflow
Solution 3 - Docker	Rambou	View Answer on Stackoverflow
Solution 4 - Docker	pras1101	View Answer on Stackoverflow

docker compose build single container

Docker Problem Overview

Docker Solutions

Solution 1 - Docker

Solution 2 - Docker

Solution 3 - Docker

Solution 4 - Docker

How can I `await` on an Rx Observable?

How to get access to webpack-dev-server from devices in local network?

Attributions