如何从周四到周三查询上周？(How do I query Last Week From Thursday to Wednesday?)

 您docker-compose.yml文件格式错误，因为您没有收到任何错误，我会假设您将错误粘贴在这里，这是带有固定缩进的版本： 
 
web:
  build: .
  volumes:
    - .:/app
  volumes_from:
    - box
  ports:
    - "3000:3000"

box:
  image: busybox
  volumes:
    - /node_modules
 
 您的Dockerfile有一个错误，您缺少ENTRYPOINT和/或CMD节，而不是您正在使用错误意图的RUN节，这是一个工作的Dockerfile ，其中应用了修复： 
 
FROM node:8.7.0

# The base node image sets a very verbose log level.
ENV NPM_CONFIG_LOGLEVEL warn

WORKDIR /tmp
COPY package.json /tmp/
RUN npm install

WORKDIR /app
ADD . /app
RUN cp -a /tmp/node_modules /app/

#ENV PORT=3000
EXPOSE 3000
CMD npm start
 
 您的Dockerfile停止了Dockerfile docker-compose在Dockerfile映像构建阶段的执行，因为RUN npm start是一个启动并监听直到停止的进程（因为您希望它启动节点应用程序并侦听连接）导致docker-compose永远不要完成docker镜像创建步骤，更不用说其他步骤，比如创建所需的容器并完成整个docker-compose运行时进程。 
 
 简而言之： 
 
 当你使用RUN它意味着运行一个命令做一些工作并返回某个时间继续构建过程，它应该返回并退出0的代码，并且该过程将继续到下一个Dockerfile节，或者返回另一个退出代码和构建过程将失败并出现错误。 
 
 当您使用CMD您告诉docker image从此映像启动的所有容器的起始命令是什么（它也可以在运行时使用docker run覆盖）。 它与ENTRYPOINT节紧密相关，但对于基本用法，您可以使用默认安全。 
 
 进一步阅读： ENTRYPOINT ， CMD和RUN 

Your docker-compose.yml file has bad formatting, since you are not getting any errors i will assume you pasted it here wrong, here is the version with the fixed indenting: 
 
web:
  build: .
  volumes:
    - .:/app
  volumes_from:
    - box
  ports:
    - "3000:3000"

box:
  image: busybox
  volumes:
    - /node_modules
 
Your Dockerfile has a bug, you are missing the ENTRYPOINT and/or CMD stanzas, instead you are using the RUN stanza with the wrong intent, here is a working Dockerfile with the fix applied:
 
FROM node:8.7.0

# The base node image sets a very verbose log level.
ENV NPM_CONFIG_LOGLEVEL warn

WORKDIR /tmp
COPY package.json /tmp/
RUN npm install

WORKDIR /app
ADD . /app
RUN cp -a /tmp/node_modules /app/

#ENV PORT=3000
EXPOSE 3000
CMD npm start
 
Your Dockerfile halted the execution of docker-compose at the docker image building stage because of the RUN npm start which is a process that starts and listens until stopped (because you want it to start your node app and listen for connections) causing docker-compose to never finish the docker image creating step, let alone the other steps like creating the needed containers and finish the entire docker-compose runtime process.
 
In short:
 
When you use RUN it is meant to run a command do some work and return sometime to continue the building process, it should return and exit code of 0 and the process will move on to the next Dockerfile stanza, or return another exit code and the building process will fail with an error.
 
When you use CMD you tell the docker image what is the starting command of all the containers started from this image (it can also be overridden at run time with docker run). It is tightly related to the ENTRYPOINT stanza, but for basic usage you are safe with the default.
 
Further reading: ENTRYPOINT, CMD and RUN