docker-compose

问题 I've been trying to deploy my docker consisted of Django, Postgresql and Nginx. It works fine when I do sudo docker-compose up However when deploy it on AWS EB, it gives me could not translate host name "db" to address: Name or service not known What I've done is I pushed my docker to docker hub using sudo docker build -t myname/dockername -f Dockerfile . and I simply do eb deploy File Structure myproject myproject settings.py urls.py ... Dockerfile Dockerrun.aws.json manage.py requirements

问题 We have a Rails app with MySQL as DB. The db part of docker-compose.yml looks like db: image: mysql env_file: - ma.env volumes: - ./dump-db:/docker-entrypoint-initdb.d - ./my.cnf:/etc/mysql/my.cnf restart: always ports: - "3306:3306" environment: - MYSQL_HOST= and under ./dump-db folder there actually is an sql-dump of our db. Problem is, we need to have that exact dump loaded each and every time docker-compose up is run. MySQL docker image works in such a way, that it stores it's data on

问题 I'm very new for docker, now I am trying to run django with mariadb in docker through docker-compose, but I always get this error: I use Docker version 17.09.1-ce, build 19e2cf6 , docker-compose version 1.18.0, build 8dd22a9 django.db.utils.OperationalError: (2003, 'Can\'t connect to MySQL server on \'mariadb55\' (111 "Connection refused")') I can connect db correctly after run docker-compose up db in local or remote, and I even can run python manage.py runserver 0.0.0.0:6001 correctly in

问题 I'm very new for docker, now I am trying to run django with mariadb in docker through docker-compose, but I always get this error: I use Docker version 17.09.1-ce, build 19e2cf6 , docker-compose version 1.18.0, build 8dd22a9 django.db.utils.OperationalError: (2003, 'Can\'t connect to MySQL server on \'mariadb55\' (111 "Connection refused")') I can connect db correctly after run docker-compose up db in local or remote, and I even can run python manage.py runserver 0.0.0.0:6001 correctly in

问题 I'm very new for docker, now I am trying to run django with mariadb in docker through docker-compose, but I always get this error: I use Docker version 17.09.1-ce, build 19e2cf6 , docker-compose version 1.18.0, build 8dd22a9 django.db.utils.OperationalError: (2003, 'Can\'t connect to MySQL server on \'mariadb55\' (111 "Connection refused")') I can connect db correctly after run docker-compose up db in local or remote, and I even can run python manage.py runserver 0.0.0.0:6001 correctly in

问题 Is there any way to cache docker-compose so that it will not build again and again? here is my action workflow file: name: Github Action on: push: branches: - staging jobs: test: runs-on: ubuntu-18.04 steps: - uses: actions/checkout@v1 - name: Bootstrap app on Ubuntu uses: actions/setup-node@v1 with: node-version: '12' - name: Install global packages run: npm install -g yarn prisma - name: Install project deps if: steps.cache-yarn.outputs.cache-hit != 'true' run: yarn - name: Build docker

问题 Is there any way to cache docker-compose so that it will not build again and again? here is my action workflow file: name: Github Action on: push: branches: - staging jobs: test: runs-on: ubuntu-18.04 steps: - uses: actions/checkout@v1 - name: Bootstrap app on Ubuntu uses: actions/setup-node@v1 with: node-version: '12' - name: Install global packages run: npm install -g yarn prisma - name: Install project deps if: steps.cache-yarn.outputs.cache-hit != 'true' run: yarn - name: Build docker

问题 Is there any way to cache docker-compose so that it will not build again and again? here is my action workflow file: name: Github Action on: push: branches: - staging jobs: test: runs-on: ubuntu-18.04 steps: - uses: actions/checkout@v1 - name: Bootstrap app on Ubuntu uses: actions/setup-node@v1 with: node-version: '12' - name: Install global packages run: npm install -g yarn prisma - name: Install project deps if: steps.cache-yarn.outputs.cache-hit != 'true' run: yarn - name: Build docker

问题 I am having 2 docker containers for php app and mysql. Both are working perfectly individually. I can access my php app at localhost:8000 and can connect mysql at localhost:3306 using MySQL Workbench. But, my php app which is inside the container is not able to connect to the mysql db which is inside another container. My docker-compose.yml file is as follows: version: '3' services: website: container_name: php-app image: php-app build: context: ./ volumes: - php-app:/var/www/html/ ports: -

问题 I am working on a docker environment(docker-compose) with a jupyter notebook docker image and a postgres docker image for running ML models and using google cloud storage to store the model artifacts. Storing the models on the cloud storage works fine but i can't get to show them within the MLFlow UI. I have seen similar problems but non of the solutions used google cloud storage as the storage location for artifacts. The error message says the following Unable to list artifacts stored under