Answers: <p>After getting your site up with <code>docker-compose up</code> there is No practical reason for running <code>docker-compose up</code> again without making any changes, because the container is running.</p>
  
  <p>So docker deamon informs you there is nothing New to do. </p>
  
Answers: CC BY-SA 4.0
Answers: 2019-06-17T00:02:15.087Z
Answers: But I get this error even after `docker-compose stop` or `docker-compose down` command
Answers: Rikipm
Answers: CC BY-SA 4.0
Answers: 2019-06-17T07:02:34.153Z
Answers: Did you check if all containers are stopped successfuly?
Answers: workaround
Answers: CC BY-SA 4.0
Answers: 2019-06-17T13:02:40.813Z
Answers: Yes,`docker ps` say that  they are stopped
Answers: Rikipm
Answers: CC BY-SA 4.0
Answers: 2019-06-16T22:15:51.947Z
Answers: 2019-06-16T22:15:51.947Z
Answers: workaround
Body: <p>I have docker-compose file with one image (httpd) and one volume that look into ./ folder (It contains only one <code>index.html</code> static file). When I start my computer I launch this image with</p>
  
  <pre><code>docker-compose up
  </code></pre>
  
  <p>And it works, I see message</p>
  
  <pre><code>Starting mysiteloc_app_1        ... done
  </code></pre>
  
  <p>And can access it via localhost.</p>
  
  <p>But when I wait several hours (seriously, I do nothing, for experiment I just wait 3 hours without touching keyboard or mouse) and try to use</p>
  
  <pre><code>docker-compose up
  </code></pre>
  
  <p>I get message</p>
  
  <pre><code>mysiteloc_redis_1 is up-to-date
  </code></pre>
  
  <p>But if I restart docker daemon all works nice. What the problem? Docker reference say that if i get <code>up-to date</code> message I changed volume or docker-compose.yml and need to rebuild, but firstly I dont changed anything, secondly why after reboot it works without rebuild?</p>
  
  <p>P.S: When I write this message I realised that use <code>httpd:latest</code> image. Problem may be related with minor httpd updates? But then why I dont need rebuild after restarting daemon?</p>
  
Comments: CC BY-SA 4.0
Comments: 2019-06-16T19:53:31.063Z
Comments: Can you clarify what your question is? Also, is your title correct? It doesn't make alot of sense.
Comments: Oxymoron
Comments: CC BY-SA 4.0
Comments: 2019-06-16T22:00:53.507Z
Comments: My problem is that without daemon restart docker cant launch container.
  
  Title is really incorrect,I corrected it
Comments: Rikipm
Comments: CC BY-SA 4.0
Comments: 2019-06-17T13:39:01.503Z
Comments: Could you provide the docker-compose.yml And the corresponding dockerfiles?
Comments: workaround
Tags: <docker><docker-compose>
Title: Why Docker cant launch container?
UserDisplayName: Rikipm
ThreadText: # Why Docker cant launch container?
  
  (Asked by: username_0 on 2019-06-16)
  
  I have docker-compose file with one image (httpd) and one volume that look into ./ folder (It contains only one `index.html` static file). When I start my computer I launch this image with
  
  ```
  docker-compose up
  
  ```
  
  And it works, I see message
  
  ```
  Starting mysiteloc_app_1        ... done
  
  ```
  
  And can access it via localhost.
  
  But when I wait several hours (seriously, I do nothing, for experiment I just wait 3 hours without touching keyboard or mouse) and try to use
  
  ```
  docker-compose up
  
  ```
  
  I get message
  
  ```
  mysiteloc_redis_1 is up-to-date
  
  ```
  
  But if I restart docker daemon all works nice. What the problem? Docker reference say that if i get `up-to date` message I changed volume or docker-compose.yml and need to rebuild, but firstly I dont changed anything, secondly why after reboot it works without rebuild?
  
  P.S: When I write this message I realised that use `httpd:latest` image. Problem may be related with minor httpd updates? But then why I dont need rebuild after restarting daemon?
  
  **Tags:** docker, docker-compose
  
  > **Comments:**
  > **username_1**: Can you clarify what your question is? Also, is your title correct? It doesn't make alot of sense.  
  > **username_0**: My problem is that without daemon restart docker cant launch container.  Title is really incorrect,I corrected it  
  > **username_2**: Could you provide the docker-compose.yml And the corresponding dockerfiles?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2019-06-16. Score: 1
  
  After getting your site up with `docker-compose up` there is No practical reason for running `docker-compose up` again without making any changes, because the container is running.
  
  So docker deamon informs you there is nothing New to do.
  
  > **Comments:**
  > **username_0**: But I get this error even after `docker-compose stop` or `docker-compose down` command  
  > **username_2**: Did you check if all containers are stopped successfuly?  
  > **username_0**: Yes,`docker ps` say that  they are stopped  
  
  ---
  
  