docker-compose

问题 I am here just to share some experience with java DDP Client Meteor and Docker Hello I am accessing to a meteor docker container from a J2EE docker container and it fails because there are some trouble at the connection with the server name (corresponding to "meteor" in my compose file) and the port "82". In this case it doesn't take into account the port and it replaces it with a default value 80... so the connection fails... 回答1: WHY ? because URI don't handle domain name without dots e.g.

问题 Updating the post with all files required to recreate the setup. – Still the same problem. Not able to access service running in container. FROM python:3 RUN apt-get update RUN apt-get install -y ruby rubygems RUN gem install sinatra WORKDIR /app ADD . /app/ EXPOSE 4567 CMD ruby hei.rb -p 4567 hei.rb require 'sinatra' get '/' do 'Hello world!' end docker-compose.yml version: '2' services: web: build: . ports: - "4567:4567" I'm starting the party by running docker-compose up --build . docker

问题 If I kill my docker daemon process and then restart it, any containers that were running are now listed with Exited status and cannot be restarted using docker-compose as it will complain about the container name already being in use. Docker containers can be started again using docker start but this could be hard when you've many containers. Is there any way to restart the docker daemon, leave containers running (so as to not disrupt traffic) and have the daemon reattach to the containers?

问题 I'm relatively new to docker and docker-compose so I made this file version: '3' services: web: image: nginx:latest ports: - "8050:80" volumes: - ./code:/code - ./site.conf:/etc/nginx/conf.d/default.conf links: - php php: image: php:7.3-fpm-alpine3.9 command: apk --update add php7-mysqli volumes: - ./code:/code db: image: mysql command: --default-authentication-plugin=mysql_native_password restart: always ports: - 3306:3306 environment: MYSQL_ROOT_PASSWORD: example adminer: image: adminer

问题 There's a private gitlab server in my company, which is created by using the docker-compose file of sameersbn/docker-gitlab:10.5.6. Today when I try to move the mounted volumes to a new disk, I accidentally created 2 sets of docker containers( sameersbn/gitlab:10.5.6 , sameersbn/postgresql:9.6-2 , and sameersbn/redis:2.8.4 ) that use the same disk volumes. Then a moment later, someone in the company told me that his project at gitlab returns 404 error. I've checked the PostgreSQL database and

问题 I try to run docker-compose up to build django app but I got this error message. Building web Step 1/6 : FROM python:2.7 ---> bfa54426aeda Step 2/6 : ENV PYTHONUNBUFFERED 1 ---> Using cache ---> 52295fd3b228 Step 3/6 : RUN mkdir /deniz1 ---> Using cache ---> dff17bbae4d8 Step 4/6 : WORKDIR /deniz1 ---> Using cache ---> 0f95497fe436 Step 5/6 : ADD . /deniz1/ ---> Using cache ---> 750b3033f58d Step 6/6 : RUN pip install --upgrade -r requirements.txt ---> Running in 0559d5fd6935 Processing .

问题 I have a number of collections with schema validation rules that I would like to use to populate a database on the startup of a docker container using the docker-compose up --build command. Since there are so many collections, I have separated the collections into different js files for hopefully clean directory structure and code organization and readability. Each js file exports a variable of the form export const CollectionDeps = ["NameOfCollection", obj]; where the object is the json

问题 Below is the dockerfile which is stored as image tag somehub/someapp-specs : FROM ubuntu:trusty MAINTAINER Developer team <developerteam@abc.com> # Prevent dpkg source ENV TERM=xterm-256color # Set mirrors to ca RUN sed -i "s/http:\/\/archive./http:\/\/ca.archive./g" /etc/apt/sources.list # Install node.js RUN apt-get update && \ apt-get install curl -y && \ curl -sL http://deb.nodesource.com/setup_4.x | sudo -E bash - && \ apt-get install -y nodejs COPY . /app WORKDIR /app # Install

问题 I tried to use docker-compose to run nsq, the docker-compose.yml as below: version: '3' services: nsqlookupd: image: nsqio/nsq command: /nsqlookupd ports: - "4160:4160" - "4161:4161" nsqd: image: nsqio/nsq command: /nsqd --lookupd-tcp-address=nsqlookupd:4160 depends_on: - nsqlookupd ports: - "4150:4150" - "4151:4151" nsqadmin: image: nsqio/nsq command: /nsqadmin --lookupd-http-address=nsqlookupd:4161 depends_on: - nsqlookupd ports: - "4171:4171" I am using the nsq client go-nsq to produce and

问题 I am using Docker Swarm and docker-compose to setup my Fabric (v1.1) and Composer (v0.19.18) networks. I wanted to test how my Swarm/Fabric networks would respond to a host/ec2 failure, so I manually reboot the host which is running the fabric-ca, orderer, and peer0 containers. Before the reboot, everything runs perfectly with respect to issuing identities. After the reboot, though all of the Fabric containers are restarted and appear to be functioning properly, I am unable to issue