docker-compose

问题 The app I'm making is written in ES6 and other goodies is transpiled by webpack inside a Docker container. At the moment everything works from creating the inner directory, installing dependencies, and creating the compiled bundle file. When running the container instead, it says that dist/bundle.js does not exist. Except if I create the bundle file in the host directory, it will work. I've tried creating a volume for the dist directory at it works the first time, but after making changes and

问题 The app I'm making is written in ES6 and other goodies is transpiled by webpack inside a Docker container. At the moment everything works from creating the inner directory, installing dependencies, and creating the compiled bundle file. When running the container instead, it says that dist/bundle.js does not exist. Except if I create the bundle file in the host directory, it will work. I've tried creating a volume for the dist directory at it works the first time, but after making changes and

问题 I am currently running a docker-compose stack for basic integration tests with a protractor test runner, a nodejs server serving a web page and a wildfly server serving a java backend. The stack is run from a dind(docker in docker) container in my build server(concourse ci). But it appears that the containers does not terminate on finishing the protractor tests. So since the containers for wildfly, and nodejs are still running the build task never finishes... How can I make the compose end in

问题 I have two containers - one containing a react app, another a flask app. I can build both using the below docker-compose file and their respective Dockerfiles, and am able to access each via the browser on the ports specified. However, my React app's API calls to Flask are not being retrieved (they work without Docker in the picture). Any suggestions are greatly appreciated! Docker-compose version: '3.7' services: middleware: build: ./middleware command: python main.py run -h 0.0.0.0 volumes:

问题 I have two containers - one containing a react app, another a flask app. I can build both using the below docker-compose file and their respective Dockerfiles, and am able to access each via the browser on the ports specified. However, my React app's API calls to Flask are not being retrieved (they work without Docker in the picture). Any suggestions are greatly appreciated! Docker-compose version: '3.7' services: middleware: build: ./middleware command: python main.py run -h 0.0.0.0 volumes:

问题 I have two containers - one containing a react app, another a flask app. I can build both using the below docker-compose file and their respective Dockerfiles, and am able to access each via the browser on the ports specified. However, my React app's API calls to Flask are not being retrieved (they work without Docker in the picture). Any suggestions are greatly appreciated! Docker-compose version: '3.7' services: middleware: build: ./middleware command: python main.py run -h 0.0.0.0 volumes:

问题 I have some containers which all of them have the always restart value in the docker-compose file like this: version: "3.7" services: container: image: ghost:latest container_name: some_container restart: always depends_on: - ... ports: - ... ... As soon as the OS (Flatcar Linux / CoreOS) has updated itself none of the containers restart. But if I just do $ sudo docker ps all of the containers starts at once. Whats up with that and how do I fix it so my containers automatically restarts after

问题 I have some containers which all of them have the always restart value in the docker-compose file like this: version: "3.7" services: container: image: ghost:latest container_name: some_container restart: always depends_on: - ... ports: - ... ... As soon as the OS (Flatcar Linux / CoreOS) has updated itself none of the containers restart. But if I just do $ sudo docker ps all of the containers starts at once. Whats up with that and how do I fix it so my containers automatically restarts after

问题 I currently use docker for my backend, and when I first start them up with docker-compose up I get log outputs of all 4 dockers at once, so I can see how they are interacting with each other when a request comes in. Looking like this, one request going from nginx to couchdb The issue is now that I am running on GCE with load balancing, when a new VM spins up, it auto starts the dockers and runs normally, I would like to be able to access a load balanced VM and view the live logs, but I can

问题 I currently use docker for my backend, and when I first start them up with docker-compose up I get log outputs of all 4 dockers at once, so I can see how they are interacting with each other when a request comes in. Looking like this, one request going from nginx to couchdb The issue is now that I am running on GCE with load balancing, when a new VM spins up, it auto starts the dockers and runs normally, I would like to be able to access a load balanced VM and view the live logs, but I can