For normal production (on a server), use the default `daemon on;` directive so the Nginx server will start in the background. In this way Nginx and other services are running and talking to each other. One server runs many services.

For **Docker containers** (or for debugging), the `daemon off;` directive tells Nginx to stay in the foreground.  For containers this is useful as best practice is for one container = one process. One server (container) has only one service.

Setting `daemon off;` is also useful if there&#39;s a 3rd party tool like [Supervisor][1] controlling your services.  Supervisor lets you stop/start/get status for bunches of services at once.

I use `daemon off;` for tweaking my Nginx config, then cleanly killing the service and restarting it.  This lets me test configurations rapidly. When done I use the default `daemon on;`.


  [1]: http://supervisord.org/

As mentioned in [this SO thread][0], it appears that &quot;that initial process immediately spawns a master nginx process and some workers, and then quits. Since Docker is only watching the PID of the original command, the container then halts.&quot;

Regarding the [`daemon off` directive][2], it appears that it was originally intended for nginx code development, though is safe for production post version 1.0.9, per the [FAQ][1].

[0]: https://stackoverflow.com/questions/18861300/how-to-run-nginx-within-docker-container-without-halting
[1]: http://nginx.org/en/docs/faq/daemon_master_process_off.html
[2]: http://nginx.org/en/docs/ngx_core_module.html#daemon

I rejected a binary i had which was 1.0 (1.0).
The status went into Rejected by developer.

I went to upload a new binary and ran into this issue, i then saw that i needed to increment my build.

I increased both the app version and build to 1.1, this was a mistake.

I got some error about the app version not matching, understood.

Then i tried app version 1.0 and many different build numbers.
1.1, 1.0.1, 1.2, 1.3, 1.0.3..nothing works.
I keep getting this error. There is only one build listed on itunes connect (1.0)

I tried submitting with no binary and it says i need one.

I even tried changing the app version to 1.1 in itunes connected and then uploading
1.1 (1.0) and that fails as well with the same duplicate issue.

Anyone ever have this issue?

![Screenshot for error][1]


  [1]: http://i.stack.imgur.com/PFg4C.png

Getting ITMS-4238 &quot;Redundant Binary Upload&quot; error no mater what I change the build version or app version to

Recently, in our company, we decided to use _Ansible_ for deployment and continuous integration. But when I started using Ansible I didn&#39;t find modules for building Java projects with Maven, or modules for running JUnit tests, or JMeter tests. 

So, I&#39;m in a doubtful state: it may be I&#39;m using Ansible in a wrong way. 

When I looked at Jenkins, it can do things like build, run tests, deploy. The missing thing in Hudson is creating/deleting an instance in cloud environments like AWS.

So, in general, for what purposes do we need to use Ansible/Jenkins? For CI do I need to use a combination of Ansible and Jenkins?

Please throw some light on correct usage of Ansible. 

Is Ansible a replacement for a CI tool like Hudson/Jenkins?

This is my first web-server administration experience and I want to build docker container which uses nginx as a web-server. In all docker tutorial `daemon off;` option is put into main `.conf` file but explanation about it is omitted.

I search on the internet about it and I don&#39;t understand what is the difference between `daemon on;` and `daemon off;` options. Some people mentioned that `daemon off;` is for production, why?

Can you explain, what is the difference between this two options, and why I should use `daemon off;` on production?

What is the difference between nginx daemon on/off option?

This is my first web-server administration experience and I want to build docker container which uses nginx as a web-server. In all docker tutorial <code>daemon off;</code> option is put into main <code>.conf</code> file but explanation about it is omitted.
I search on the internet about it and I don't understand what is the difference between <code>daemon on;</code> and <code>daemon off;</code> options. Some people mentioned that <code>daemon off;</code> is for production, why?
Can you explain, what is the difference between this two options, and why I should use <code>daemon off;</code> on production?

I&#39;m getting the following error on my chrome console:

    GET http://localhost/grunt/vendor/angular/angular.js net::ERR_CONTENT_LENGTH_MISMATCH 


This only happens when a simultaneous requests are shot towards nginx e.g. when the browsers cache is empty and the whole app loads. Loading the resource above as a single requests succeeds.


Here are the headers to this requests, copied from Chrome:

   

    Remote Address:127.0.0.1:80
    Request URL:http://localhost/grunt/vendor/angular/angular.js
    Request Method:GET
    Status Code:200 OK
    Request Headersview source
    Accept:*/*
    Accept-Encoding:gzip,deflate,sdch
    Accept-Language:en-US,en;q=0.8,de;q=0.6,pl;q=0.4,es;q=0.2,he;q=0.2,gl;q=0.2
    Cache-Control:no-cache
    Connection:keep-alive
    Cookie:gs_u_GSN-265185-D=1783247335:2567:5000:1377697930719
    Host:localhost
    Pragma:no-cache
    Referer:http://localhost/grunt/
    User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.122 Safari/537.36
    Response Headersview source
    Accept-Ranges:bytes
    Cache-Control:public, max-age=0
    Connection:keep-alive
    Content-Length:873444
    Content-Type:application/javascript
    Date:Tue, 23 Sep 2014 11:08:19 GMT
    ETag:&quot;873444-1411465226000&quot;
    Last-Modified:Tue, 23 Sep 2014 09:40:26 GMT
    Server:nginx/1.6.0

the real size of the file:

    $ ll vendor/angular/angular.js
    -rw-rw-r--  1 xxxx  staff  873444 Aug 30 07:21 vendor/angular/angular.js


As you can see `Content-Length` and the real size of the file are the same, so that&#39;s weird

And the nginx configuration to this proxy:

    location /grunt/ {
        proxy_pass  http://localhost:9000/;
    }

Any ideas?

Thanks


EDIT: found more info on the error log:

    2014/09/23 13:08:19 [crit] 15435#0: *8 open() &quot;/usr/local/var/run/nginx/proxy_temp/1/00/0000000001&quot; failed (13: Permission denied) while reading upstream, client: 127.0.0.1, server: localhost, request: &quot;GET /grunt/vendor/angular/angular.js HTTP/1.1&quot;, upstream: &quot;http://127.0.0.1:9000/vendor/angular/angular.js&quot;, host: &quot;localhost&quot;, referrer: &quot;http://localhost/grunt/&quot;

ERR_CONTENT_LENGTH_MISMATCH on nginx and proxy on Chrome when loading large files

I&#39;m not able to setup SSL. I&#39;ve Googled and I found a few solutions but none of them worked for me. I need some help please...

Here&#39;s the error I get when I attempt to restart nginx:

    root@s17925268:~# service nginx restart
    Restarting nginx: nginx: [emerg] SSL_CTX_use_PrivateKey_file(&quot;/etc/nginx/conf.d/ssl/ssl.key&quot;) failed (SSL: error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch)
    nginx: configuration file /etc/nginx/nginx.conf test failed

My certificate is from StartSSL and is valid for 1 year.

Here&#39;s what I tested:

- The certificate and private key has no trailing spaces.
- I&#39;m not using the default server.key file.
- I checked the nginx.conf and the
   directives are pointing to the correct private key and certificate.

I also checked the modulus, and I get a different modulus for both key and certificate.

Thank you for your help. :)

SSL: error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch

I want to increase the `maximum file size` that can be uploaded.  
After doing some research online, I found that you have to edit the file &#39;nginx.conf&#39;.  
The only way I can currently access this file is by going through Putty and typing in the command:

    vi /etc/nginx/nginx.conf

This will open the file but I have 2 questions now:

1.  How do I edit this file?
2.  I found online that you have to add the following line of code:
    

`client_max_body_size 8M;`


Where would I put this line of code in `nginx.conf`?

How to edit nginx.conf to increase file size upload

I understand all the column of this app&#39;s access log- IP, date, request, response code and... except the next column is what I don&#39;t understand (in the example below, 177, 4223, 4356). What is this stands for?

    66.249.65.159 - - [06/Nov/2014:19:10:38 +0600] &quot;GET /news/53f8d72920ba2744fe873ebc.html HTTP/1.1&quot; 404 177 &quot;-&quot; &quot;Mozilla/5.0 (iPhone; CPU iPhone OS 6_0 like Mac OS X) AppleWebKit/536.26 (KHTML, like Gecko) Version/6.0 Mobile/10A5376e Safari/8536.25 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)&quot;
    66.249.65.3 - - [06/Nov/2014:19:11:24 +0600] &quot;GET /?q=%E0%A6%AB%E0%A6%BE%E0%A7%9F%E0%A6%BE%E0%A6%B0 HTTP/1.1&quot; 200 4223 &quot;-&quot; &quot;Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)&quot;
    66.249.65.62 - - [06/Nov/2014:19:12:14 +0600] &quot;GET /?q=%E0%A6%A6%E0%A7%8B%E0%A7%9F%E0%A6%BE HTTP/1.1&quot; 200 4356 &quot;-&quot; &quot;Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)&quot;


Edit: I&#39;ve googled, but couldn&#39;t find any answer.


Nginx understanding access log column

**Update II**

It&#39;s now July 16th, 2015 and things have changed again. I&#39;ve discovered this automagical container from Jason Wilder: https://github.com/jwilder/nginx-proxy and it solves this problem in about as long as it takes to docker run the container. This is now the solution I&#39;m using to solve this problem. 


**Update**

It&#39;s now July of 2015 and things have change drastically with regards to networking Docker containers. There are now many different offerings that solve this problem (in a variety of ways).

You should use this post to gain a basic understanding of the docker --link approach to service discovery, which is about as basic as it gets, works very well, and actually requires less fancy-dancing than most of the other solutions. It is limited in that it&#39;s quite difficult to network containers on separate hosts in any given cluster, and containers cannot be restarted once networked, but does offer a quick and relatively easy way to network containers on the same host. It&#39;s a good way to get an idea of what the software you&#39;ll likely be using to solve this problem is actually doing under the hood.

Additionally, you&#39;ll probably want to also check out Docker&#39;s nascent network, Hashicorp&#39;s consul, Weaveworks weave, Jeff Lindsay&#39;s progrium/consul &amp; gliderlabs/registrator, and Google&#39;s Kubernetes.

There&#39;s also the CoreOS offerings that utilize etcd, fleet, and flannel.

And if you really want to have a party you can spin up a cluster to run Mesosphere, or Deis, or Flynn.

If you&#39;re new to networking (like me) then you should get out your reading glasses, pop &quot;Paint The Sky With Stars — The Best of Enya&quot; on the Wi-Hi-Fi, and crack a beer — it&#39;s going to be a while before you really understand exactly what it is you&#39;re trying to do. Hint: You&#39;re trying to implement a Service Discovery Layer in your Cluster Control Plane. It&#39;s a very nice way to spend a Saturday night.

It&#39;s a lot of fun, but I wish I&#39;d taken the time to educate myself better about networking in general before diving right in. I eventually found a couple posts from the benevolent Digital Ocean Tutorial gods: Introduction to Networking Terminology and Understanding ... Networking. I suggest reading those a few times first before diving in.

Have fun!



**Original Post**

I can&#39;t seem to grasp port mapping for `Docker` containers. Specifically how to pass requests from Nginx to another container, listening on another port, on the same server.

I&#39;ve got a Dockerfile for an Nginx container like so:

    FROM ubuntu:14.04
    MAINTAINER Me &lt;me@myapp.com&gt;
    
    RUN apt-get update &amp;&amp; apt-get install -y htop git nginx
    
    ADD sites-enabled/api.myapp.com /etc/nginx/sites-enabled/api.myapp.com
    ADD sites-enabled/app.myapp.com /etc/nginx/sites-enabled/app.myapp.com
    ADD nginx.conf /etc/nginx/nginx.conf
    
    RUN echo &quot;daemon off;&quot; &gt;&gt; /etc/nginx/nginx.conf
    
    EXPOSE 80 443
    
    CMD [&quot;service&quot;, &quot;nginx&quot;, &quot;start&quot;]

&lt;br&gt;&lt;br&gt;
And then the `api.myapp.com` config file looks like so:

    upstream api_upstream{
    
    	server 0.0.0.0:3333;
    
    }
    
    
    server {
    
    	listen 80;
    	server_name api.myapp.com;
    	return 301 https://api.myapp.com/$request_uri;
    
    }
    
    
    server {
    
    	listen 443;
    	server_name api.mypp.com;
    	
    	location / {
    
        	proxy_http_version 1.1;
    		proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection &#39;upgrade&#39;;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
    		proxy_cache_bypass $http_upgrade;
    		proxy_pass http://api_upstream;
    	
    	}
    
    }

And then another for `app.myapp.com` as well.

And then I run:

    sudo docker run -p 80:80 -p 443:443 -d --name Nginx myusername/nginx

&lt;br&gt;
And it all stands up just fine, but the requests are not getting passed-through to the other containers/ports. And when I ssh into the Nginx container and inspect the logs I see no errors.

Any help?

How to configure Docker port mapping to use Nginx as an upstream proxy?

As you can tell by my question, I&#39;m new to this...

I built my first website, I set up my first Node.js server to serve it and then pushed everything live on EC2.

I tested everything on my EC2 IP address and everything seems to be working.

Now up until now, I&#39;ve been testing my app locally so it makes sense that whenever I closed the terminal, app.js would stop running so nothing would be served on localhost.

Now that my server is on EC2, the same thing happens (&quot;obviously&quot; one could say..) whenever I close my terminal.

So my question is how do I keep my Node.js server running on EC2 for like... forever..so that my site stays live.. forever :)

I read something about a node module called &quot;forever&quot; but I&#39;m wondering (being new and all..) why isn&#39;t this &quot;forever&quot; functionality a default setting of the Node.js-EC2 system ?

I mean, correct me if I&#39;m wrong, but isn&#39;t the whole point of setting up a web server and pushing it live to have it stay live forever? Isn&#39;t that what servers are supposed to do anyway (infinitely listening for requests) ? And if that&#39;s the case why do we need extra modules/settings to achieve that ?

Thanks for your help.. As you can tell I&#39;m not only looking for a solution but an explanation as well because I got really confused.. :-) 



**EDIT** (a few details you might need) - After installing my app on EC2 these are the steps that I follow on the terminal (The app is running on `Amazon Linux` by the way) :
   
 - I type ssh -i xxxxxxxxxxx.pem ec2-user@ec2-xx-xx-xx-x.eu-west-1.compute.amazonaws.com on the
   terminal
   
 - After logging onto the Amazon machine I then go to the relevant folder and execute node app.js
   
 - There are 3 folders in the machine : `node`, `node_modules` and `*name of my app*`

 - `app.js` resides in `*name of my app*`

 - After that, the site goes live on my EC2 IP
   
 - Once I close the terminal, everything is switched off

How do I leave Node.js server on EC2 running forever?

I&#39;m trying to figure out what is the full complete configuration of an httpd setup.  

All the configurations files are scattered in different files (/etc/httpd/conf.d, httpd.conf, various mod configs)  

Is there a way to list the final httpd configuration?  
Like the whole running setup configuration in a single file?

How can I view the complete httpd configuration?

&gt; HTTP/1.1 has served the Web well for more than fifteen years, but its
&gt; age is starting to show.

Can anybody explain what is the **main difference** between HTTP 1.1 and 2.0?

Is there any change in the transport protocol?


What is the difference between HTTP 1.1 and HTTP 2.0?

I have installed the Windows 10 Insider Program. Everything works, except Apache. When I try to start it, it says that port 80 is blocked. Is there a way to unblock it or **tell Apache to use another port instead?**

I was using Windows 7 before. I had trouble with port 80 with skype, but i have disabled it.

Apache Server (xampp) doesn&#39;t run on Windows 10 (Port 80)

I am using nginx and node server to serve update requests. I get a gateway timeout when I request an update on large data. I saw this error from the nginx error logs :

&gt; 2016/04/07 00:46:04 [error] 28599#0: *1 upstream prematurely closed
&gt; connection while reading response header from upstream, client:
&gt; 10.0.2.77, server: gis.oneconcern.com, request: &quot;GET /update_mbtiles/atlas19891018000415 HTTP/1.1&quot;, upstream:
&gt; &quot;http://127.0.0.1:7777/update_mbtiles/atlas19891018000415&quot;, host:
&gt; &quot;gis.oneconcern.com&quot;

I googled for the error and tried everything I could, but I still get the error. 

My nginx conf has these proxy settings:
   

        ##
        # Proxy settings
        ##

        proxy_connect_timeout 1000;
        proxy_send_timeout 1000;
        proxy_read_timeout 1000;
        send_timeout 1000;

This is how my server is configured 

    server {
    listen 80;

    server_name gis.oneconcern.com;
    access_log /home/ubuntu/Tilelive-Server/logs/nginx_access.log;
    error_log /home/ubuntu/Tilelive-Server/logs/nginx_error.log;

    large_client_header_buffers 8 32k;
    location / {
        proxy_pass http://127.0.0.1:7777;
        proxy_redirect off;

        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection &#39;upgrade&#39;;
        proxy_set_header Host $http_host;
        proxy_cache_bypass $http_upgrade;
    }

    location /faults {
        proxy_pass http://127.0.0.1:8888;
        proxy_http_version 1.1;
        proxy_buffers 8 64k;
        proxy_buffer_size 128k;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection &#39;upgrade&#39;;
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
    }
}

I am using a nodejs backend to serve the requests on an aws server. The gateway error shows up only when the update takes a long time (about 3-4 minutes). I do not get any error for smaller updates. Any help will be highly appreciated. 

Node js code :

    app.get(&quot;/update_mbtiles/:earthquake&quot;, function(req, res){
    var earthquake = req.params.earthquake
    var command = spawn(__dirname + &#39;/update_mbtiles.sh&#39;, [ earthquake, pg_details ]);
    //var output  = [];

    command.stdout.on(&#39;data&#39;, function(chunk) {
    //    logger.info(chunk.toString());
    //     output.push(chunk.toString());
    });

    command.stderr.on(&#39;data&#39;, function(chunk) {
      //  logger.error(chunk.toString());
     //   output.push(chunk.toString());
    });

    command.on(&#39;close&#39;, function(code) {
        if (code === 0) {
            logger.info(&quot;updating mbtiles successful for &quot; + earthquake);
            tilelive_reload_and_switch_source(earthquake);
            res.send(&quot;Completed updating!&quot;);
        }
        else {
            logger.error(&quot;Error occured while updating &quot; + earthquake);
            res.status(500);
            res.send(&quot;Error occured while updating &quot; + earthquake);
        }
    });
    });

    function tilelive_reload_and_switch_source(earthquake_unique_id) {
    tilelive.load(&#39;mbtiles:///&#39;+__dirname+&#39;/mbtiles/tipp_out_&#39;+ earthquake_unique_id + &#39;.mbtiles&#39;, function(err, source) {
        if (err) {
            logger.error(err.message);
            throw err;
        }
        sources.set(earthquake_unique_id, source); 
        logger.info(&#39;Updated source! New tiles!&#39;);
    });
    }

Thank you.


Nginx upstream prematurely closed connection while reading response header from upstream, for large requests

I want to make a move to Docker, so I&#39;ve just started to mess around with it. I&#39;ve installed Docker on a VirtualBox Ubuntu 15.10 (Wily Werewolf) installation and as [suggested here][1] I then tried running a basic [nginx][2] Docker image:

    $ docker run --name mynginx1 -P -d nginx
    Cannot connect to the Docker daemon. Is the docker daemon running on this host?

So I checked out whether Docker was running:

    $ sudo service docker status
    ● docker.service - Docker Application Container Engine
       Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
       Active: active (running) since vr 2015-11-06 08:41:48 CET; 15min ago
         Docs: https://docs.docker.com
     Main PID: 7542 (docker)
       CGroup: /system.slice/docker.service
               └─7542 /usr/bin/docker daemon -H fd://
    
    nov 06 08:41:47 kramer65-VirtualBox systemd[1]: Starting Docker Application Container Engine...
    nov 06 08:41:47 kramer65-VirtualBox docker[7542]: time=&quot;2015-11-06T08:41:47.900410966+01:00&quot; level=info msg=&quot;API ...ock&quot;
    nov 06 08:41:48 kramer65-VirtualBox docker[7542]: time=&quot;2015-11-06T08:41:48.033514149+01:00&quot; level=info msg=&quot;Fire...lse&quot;
    nov 06 08:41:48 kramer65-VirtualBox docker[7542]: time=&quot;2015-11-06T08:41:48.141594321+01:00&quot; level=info msg=&quot;Defa...ess&quot;
    nov 06 08:41:48 kramer65-VirtualBox docker[7542]: time=&quot;2015-11-06T08:41:48.416294436+01:00&quot; level=warning msg=&quot;Y...it.&quot;
    nov 06 08:41:48 kramer65-VirtualBox docker[7542]: time=&quot;2015-11-06T08:41:48.565507576+01:00&quot; level=info msg=&quot;Load...rt.&quot;
    nov 06 08:41:48 kramer65-VirtualBox docker[7542]: time=&quot;2015-11-06T08:41:48.567907022+01:00&quot; level=info msg=&quot;Load...ne.&quot;
    nov 06 08:41:48 kramer65-VirtualBox docker[7542]: time=&quot;2015-11-06T08:41:48.567945214+01:00&quot; level=info msg=&quot;Daem...ion&quot;
    nov 06 08:41:48 kramer65-VirtualBox docker[7542]: time=&quot;2015-11-06T08:41:48.567969891+01:00&quot; level=info msg=&quot;Dock....9.0
    nov 06 08:41:48 kramer65-VirtualBox systemd[1]: Started Docker Application Container Engine.
    Hint: Some lines were ellipsized, use -l to show in full.

This suggests that the Docker daemon is actually already running, but to be sure I just started the Docker daemon manually:

    $ sudo docker daemon
    INFO[0000] API listen on /var/run/docker.sock           
    INFO[0000] [graphdriver] using prior storage driver &quot;aufs&quot; 
    INFO[0000] Firewalld running: false                     
    INFO[0000] Default bridge (docker0) is assigned with an IP address XXX.XX.X.X/XX. Daemon option --bip can be used to set a preferred IP address 
    WARN[0000] Your kernel does not support swap memory limit. 
    INFO[0000] Loading containers: start.                   
    
    INFO[0000] Loading containers: done.                    
    INFO[0000] Daemon has completed initialization          
    INFO[0000] Docker daemon                                 commit=76d6bc9 execdriver=native-0.2 graphdriver=aufs version=1.9.0

I then tried running the image again, but with the same result:

    $ docker run --name mynginx1 -P -d nginx
    Cannot connect to the Docker daemon. Is the docker daemon running on this host?

I tried sudo&#39;ing the command, but to no avail. What am I doing wrong here? 

  [1]: https://blog.docker.com/2015/04/tips-for-deploying-nginx-official-image-with-docker/
  [2]: http://en.wikipedia.org/wiki/Nginx




Docker command can&#39;t connect to Docker daemon

I would like to run multi-container application using `docker-compose` on Mac OS X El Capitan (v10.11.2).

However, the command `$ docker-compose up` command complains that it can&#39;t connect to the Docker daemon.

&gt; ERROR: Couldn&#39;t connect to Docker daemon - you might need to run `docker-machine start default`.

Only after executing `$ eval &quot;$(docker-machine env default)&quot;` I do have access to the `docker-compose` command.

Why is this and how can I overcome this extra step?

Couldn&#39;t connect to Docker daemon on Mac OS X

My version of OS `Ubuntu 16.04`.
I want to stop docker, so I run in the terminal:

    sudo systemctl stop docker

But this commands doesn&#39;t help me:

    gridsim1103 ~: ps ax | grep docker 
    11347 ?        Sl     0:00 containerd-shim 487e3784f983274131d37bde1641db657e76e41bdd056f43ef4ad5adc1bfc518 /var/run/docker/libcontainerd/487e3784f983274131d37bde1641db657e76e41bdd056f43ef4ad5adc1bfc518 runc
    14299 pts/2    S+     0:00 grep --color=auto docker
    29914 ?        S      0:00 sudo dockerd -H gridsim1103:2376
    29915 ?        Sl     4:45 dockerd -H gridsim1103:2376
    29922 ?        Ssl    0:24 containerd -l unix:///var/run/docker/libcontainerd/docker-containerd.sock --shim containerd-shim --metrics-interval=0 --start-timeout 2m --state-dir /var/run/docker/libcontainerd/containerd --runtime runc
    30107 ?        Sl     1:01 /usr/bin/docker-proxy -proto tcp -host-ip 188.184.80.77 -host-port 8500 -container-ip 192.17.0.2 -container-port 8500
    30139 ?        Sl     0:00 /usr/bin/docker-proxy -proto tcp -host-ip 188.184.80.77 -host-port 8400 -container-ip 192.17.0.2 -container-port 8400

Version of `docker` server is:


    Server:
     Version:      1.12.1
     API version:  1.24 (minimum version )
     Go version:   go1.6.2
     Git commit:   23cf638
     Built:        Tue, 27 Sep 2016 12:25:38 +1300
     OS/Arch:      linux/amd64
     Experimental: false


I also unsuccessfully tried:

     sudo service docker stop


How to stop docker under Linux

How can I run a shell script and immediately *background* it, however keep the ability to inspect its output any time by tailing `/tmp/output.txt`.

It would be nice if I can *foreground* the process too later.

---
### P.S.  
It would be really cool if you can also show me how to &quot;send&quot; the backgrounded process in to a GNU screen that may or may not have been initialized.

Run a shell script and immediately background it, however keep the ability to inspect its output

We all know situations when you cannot go open source and freely distribute software - and I am in one of these situations.

I have an app that consists of a number of binaries (compiled from C sources) and python code that wraps it all into a system. This app used to work as a cloud solution so users had access to app functions via network but no chance to touch the actual server where binaries and code are stored.

Now we want to deliver the &quot;local&quot; version of our system. The app will be running on PCs that our users will physically own. We know that everything could be broken, but at least want to protect the app from possible copying and reverse-engineering as much as possible.

I know that docker is a wonderful deployment tool so I wonder: it is possible to create encrypted docker containers where no one can see any data stored in the container&#39;s filesystem? Is there a known solution to this problem?

Also, maybe there are well known solutions not based on docker?

Encrypted and secure docker containers

Running out of entropy in virtualized Linux systems seems to be a common problem (e.g. https://stackoverflow.com/questions/4819359/dev-random-extremely-slow, https://stackoverflow.com/questions/5633877/getting-linux-to-buffer-dev-random). Despite of using a hardware random number generator (HRNG) the use of a an entropy gathering daemon like [HAVEGED][1] is often suggested. However an entropy gathering daemon (EGD) cannot be run inside a Docker container, it must be provided by the host.

Using an EGD works fine for docker hosts based on linux distributions like Ubuntu, RHEL, etc. Getting such a daemon to work inside boot2docker - which is based on Tiny Core Linux (TCL) - seems to be another story. Although TCL has a extension mechanism, an extension for an entropy gathering daemon [doesn&#39;t seem to be available][2].

So an EGD seems like a proper solution for running docker containers in a (production) hosting environment, but how to solve it for development/testing in boot2docker?

  [1]: http://www.issihosts.com/haveged/index.html
  [2]: http://forum.tinycorelinux.net/index.php?topic=15650.0

Since running an EGD in boot2docker seemed too difficult, I thought about simply using /dev/urandom instead of /dev/random. Using /dev/urandom is a litte less secure, but still fine for most applications which are not generating long-term cryptographic keys. At least it should be fine for development/testing inside boot2docker. 



Not enough entropy to support /dev/random in docker containers running in boot2docker

Is there any elegant way to add SSL certificates to images that have come from docker pull?.

I&#39;m looking for a simple and reproducible way of adding a file into /etc/ssl/certs and run update-ca-certificates. (This should cover ubuntu and Debian images).

I&#39;m using docker on CoreOS, and the CoreOS machine trusts the needed SSL certificates, but the docker containers obviously only have the default. 

I&#39;ve tried using `docker run --entrypoint=/bin/bash` to then add the cert and run `update-ca-certificates`, but this seems to permanently override the entry point.

I&#39;m also wondering now, would it be more elegant to just mount `/etc/ssl/certs` on the container from the host machines copy? Doing this would implicitly allow the containers to trust the same things as the host.

I&#39;m at work with an annoying proxy that resigns everything :(. Which breaks SSL and makes containers kind-of strange to work with.

Docker container SSL certificates

*Since 2014 when this question has been asked, many situations had happened and many things has changed. I&#39;m revisiting the topic again today, and I&#39;m editing this question for the 12th time to reflect the latest changes*. The question may seem long but it is arranged in the reverse chronological order, so the latest changes are at the top and feel free stop reading at any point.

The question I wanted to solve was -- how to mount host volumes into docker containers in Dockerfile during build, i.e., having the `docker run -v /export:/export` capability during `docker build`.

One reason behind it, for me, is when building things in Docker, I don&#39;t want those (`apt-get install`) caches locked in a single docker, but to share/reuse them.  

That was the main reason I was asking this question. And one more reason I&#39;m facing today is trying to make use of a huge private repo from host which I have to otherwise do `git clone` from a private repo within docker using my private ssh key, which I don&#39;t know how and haven&#39;t looked into yet.

**Latest Update:** 

The Buildkit in @BMitch&#39;s answer 

&gt; With that `RUN --mount` syntax, you can also bind mount read-only directories from the build-context...

it has now been built-in in docker (which I thought being a third-party tool), as long as yours&#39; over 18.09. Mine is 20.10.7 now --
https://docs.docker.com/develop/develop-images/build_enhancements/

&gt; To enable BuildKit builds
&gt; 
&gt; Easiest way from a fresh install of docker is to set the DOCKER_BUILDKIT=1 environment variable when invoking the docker build command, such as:
&gt; 
&gt; `$ DOCKER_BUILDKIT=1 docker build .`

Else, you&#39;ll get:

`the --mount option requires BuildKit. Refer to https://docs.docker.com/go/buildkit/ to learn how to build images with BuildKit enabled`

So it&#39;ll be the perfect solution to my second use-case as explained above.

**Update as of May 7, 2019:** 

Before docker v18.09, the correct answer should be the one that starts with:

&gt; There is a way to mount a volume during a build, but it doesn&#39;t involve Dockerfiles.

However, that was a poorly stated, organized and supported answer. When I was reinstalling my docker contains, I happened to stumble upon the following article:

**Dockerize an apt-cacher-ng service**  
[https://docs.docker.com/engine/examples/apt-cacher-ng/](https://web.archive.org/web/20140613164606/http://docker.readthedocs.org/en/v0.7.3/use/working_with_volumes/)

That&#39;s the docker&#39;s solution to this/my question, not directly but indirectly. It&#39;s the orthodox way docker suggests us to do. And I admit it is better than the one I was trying to ask here. 

Another way is, the ***newly accepted answer***, e.g., the Buildkit in v18.09.  

Pick whichever suits you. 

------

**Was:** There had been a solution -- rocker, which was not from Docker, but now that rocker is discontinued, I revert the answer back to *&quot;Not possible&quot;* again.

------

**Old Update:** So the answer is &quot;Not possible&quot;. I can accept it as an answer as I know the issue has been extensively discussed at https://github.com/docker/docker/issues/3156. I can understand that portability is a paramount issue for docker developer; but as a docker user, I have to say I&#39;m very disappointed about this missing feature. Let me close my argument with a quote from aforementioned discussion: &quot;*I would like to use Gentoo as a base image but definitely don&#39;t want &gt; 1GB of Portage tree data to be in any of the layers once the image has been built. You could have some nice a compact containers if it wasn&#39;t for the gigantic portage tree having to appear in the image during the install.*&quot; Yes, I can use wget or curl to download whatever I need, but the fact that merely a portability consideration is now forcing me to download &gt; 1GB of Portage tree each time I build a Gentoo base image is neither efficient nor user friendly. Further more, the package repository WILL ALWAYS be under /usr/portage, thus ALWAYS PORTABLE under Gentoo. Again, I respect the decision, but please allow me expressing my disappointment as well in the mean time. Thanks.

------

**Original question** in details:

From 

**Share Directories via Volumes**  
http://docker.readthedocs.org/en/v0.7.3/use/working_with_volumes/

it says that Data volumes feature &quot;have been available since version 1 of the Docker Remote API&quot;. My docker is of version 1.2.0, but I found the example given in above article not working:

    # BUILD-USING: &#160;&#160;&#160;&#160;&#160;&#160;&#160;docker build -t data .
    # RUN-USING: &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;docker run -name DATA data
    FROM &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;busybox
    VOLUME &#160;&#160;&#160;&#160;&#160;&#160;&#160;[&quot;/var/volume1&quot;, &quot;/var/volume2&quot;]
    CMD &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;[&quot;/usr/bin/true&quot;]

What&#39;s the proper way in Dockerfile to mount host-mounted volumes into docker containers,  via the VOLUME command?

    $ apt-cache policy lxc-docker
    lxc-docker:
      Installed: 1.2.0
      Candidate: 1.2.0
      Version table:
     *** 1.2.0 0
            500 https://get.docker.io/ubuntu/ docker/main amd64 Packages
            100 /var/lib/dpkg/status

    $ cat Dockerfile 
    FROM          debian:sid
    
    VOLUME        [&quot;/export&quot;]
    RUN ls -l /export
    CMD ls -l /export
    
    $ docker build -t data .
    Sending build context to Docker daemon  2.56 kB
    Sending build context to Docker daemon 
    Step 0 : FROM          debian:sid
     ---&gt; 77e97a48ce6a
    Step 1 : VOLUME        [&quot;/export&quot;]
     ---&gt; Using cache
     ---&gt; 59b69b65a074
    Step 2 : RUN ls -l /export
     ---&gt; Running in df43c78d74be
    total 0
     ---&gt; 9d29a6eb263f
    Removing intermediate container df43c78d74be
    Step 3 : CMD ls -l /export
     ---&gt; Running in 8e4916d3e390
     ---&gt; d6e7e1c52551
    Removing intermediate container 8e4916d3e390
    Successfully built d6e7e1c52551
    
    $ docker run data
    total 0
    
    $ ls -l /export | wc 
         20     162    1131

    $ docker -v
    Docker version 1.2.0, build fa7b24f



How to mount host volumes into docker containers in Dockerfile during build

I&#39;m unsure of how to name Dockerfiles. Many on GitHub use `Dockerfile` without a file extension. Do I give them a name and extension; if so what? Or do I just call them `Dockerfile`?


Content Type	Original Author	Original Content on Stackoverflow
Question	KopBob	View Question on Stackoverflow
Solution 1 - Nginx	johntellsall	View Answer on Stackoverflow
Solution 2 - Nginx	johncosta	View Answer on Stackoverflow

What is the difference between nginx daemon on/off option?

Nginx Problem Overview

Nginx Solutions

Solution 1 - Nginx

Solution 2 - Nginx

Is Ansible a replacement for a CI tool like Hudson/Jenkins?

Getting ITMS-4238 "Redundant Binary Upload" error no mater what I change the build version or app version to

Attributions