docker-compose

问题 I'm running a docker-compose file we have, I usually run it with command: docker-compose up But today I'm getting this error. ERROR: failed to register layer: symlink ../bdf441e8145a625c4ab289f13ac2274b37d35475b97680f50b7eccda4328f973/diff /var/lib/docker/overlay2/l/7O5XKRTJV6RMTXBV5DTPDOHYNX: no such file or directory 回答1: To solve this issue, you just Stop and Start docker service from terminal. # service docker stop # service docker start 回答2: Followed this answer just restarting docker

问题 I'm using jwilder/nginx-proxy with separate docker-compose.yaml . It looks like this: proxy: image: jwilder/nginx-proxy restart: always volumes: - /var/run/docker.sock:/tmp/docker.sock:ro - ./nginx/conf.d/proxy.conf:/etc/nginx/conf.d/proxy.conf:ro - /Users/marcin/Docker/local_share/certificates:/etc/nginx/certs:ro ports: - "80:80" - "443:443" container_name: proxy I'm using it for quite a long time and it's working fine when my project docker-compose.yaml looks like this: web: build: /Users

问题 Mysql is in it's own docker-compose.yml as I want a mysql server up and running that any other php application can connect to. So I do not have php and mysql in the same docker-compose.yml. From the php application, I can connect to mysql if I use the mysql container's gateway ip address by looking it up and then hard coding it into the php application. docker inspect mysql-db . But docker will change that 172... ip address each time mysql restarts so that is not ideal for development. I can

问题 I am trying to build an docker image and start the container with docker-compose inside a Jenkins pipeline. I have a custom docker image for my Jenkins where I use the Jenkins out of the box image and install Docker CE and docker compose. The Dockerfile: FROM jenkins/jenkins:2.159 USER root # create dir to save jenkins log files RUN mkdir /var/log/jenkins RUN chown -R jenkins:jenkins /var/log/jenkins #############################################################################################

问题 I have docker-compose.yml file volumes: nfs: driver: local driver_opts: type: nfs o: addr=192.168.100.1,rw device: ":/mnt/storage" my container have mounted volume with options: type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.168.100.1,mountvers=3,mountproto=tcp,local_lock=none,addr=192.168.100.1) with local_lock=none and i can't change this option to local_lock=all I tried: volumes: nfs: driver: local driver_opts:

问题 I'm following the docker-compose tutorial, to try and figure out how to get a django app to deploy: http://docs.docker.com/compose/django/ And everything's going smoothly (the app even works!) but the django project folder composeexample isn't created in my local project directory. I'm left with a working "It Works!" page after running: $ docker-compose run web django-admin.py startproject composeexample . But I can't continue to edit the composeexample/settings.py , as the tutorial suggests:

问题 I'm trying to run the NextJS on a Docker container using Dockerfile and running via docker-compose, after I changed my code in a JS file (such as index.js) the Next server did not reload. But when I've tried to run outside without using Docker (by executing the "npm run dev" command directly) the Next server did reload smoothly. I've also tried to run the server by "nodemon" command (inside a container), it did not make it either. Dockerfile: FROM node:10.14.2-alpine COPY . /home/next_app

问题 I'm trying to run the NextJS on a Docker container using Dockerfile and running via docker-compose, after I changed my code in a JS file (such as index.js) the Next server did not reload. But when I've tried to run outside without using Docker (by executing the "npm run dev" command directly) the Next server did reload smoothly. I've also tried to run the server by "nodemon" command (inside a container), it did not make it either. Dockerfile: FROM node:10.14.2-alpine COPY . /home/next_app

问题 I have a Flask application that uses SocketIO to fetch data from Postgres live. The app works fine when I run this locally. The problem arouses when I use docker-compose to host my Flask app. My JS client and flask server is hosted into a single app and on the same container. My socketio in JS is like this: var socket = io().connect(window.location.protocol + '//' + document.domain + ':' + location.port); Dockerfile: # Using python 3.7 in Alpine FROM python:3.6.5-stretch # Set the working

问题 I have been trying to get a socketio server moved over from EC2 to Docker. I have been able to connect to the socket via a web (http) client, but connecting directly to the socket via iOS or Android seems to be impossible. I read one of the issues can be the ports exposed are not actually published when using Docker. Since our mobile apps currently connect on port 8080 on our classic EC2 instance. I setup a docker-compose.yml file to try and open all ports and communication protocals, but I