docker-compose

问题 I use docker-compose file to get Elasticsearch Logstash Kibana stack. Everything works fine, docker-compose build command creates three images, about 600 MB each, downloads from docker repository needed layers. Now, I need to do the same, but at the machine with no Internet access. Downloading from respositories there is impossible. I need to create "offline installer". The best way I found is docker save image1 image2 image3 -o archivebackup.tar but created file is almost 2GB. During docker

问题 Im trying create a dev environment with php7.1 docker. And no matter what I try for some reason it says "An exception occured in driver: could not find driver ". I have searched through a lot of posts but have found no answer that solves my problem. I am using the following dockerfile and docker-compose.yml: FROM php:7.1-apache COPY dockerConfig/php.ini /usr/local/etc/php/ RUN apt-get update \ && apt-get install -y libfreetype6-dev libjpeg62-turbo-dev libpng12-dev \ && docker-php-ext

问题 I am using the official GitLab Docker image. I want to have pre-configured user accounts available in my GitLab container to be used for tests. But user accounts are saved in a volume, so I can't just commit and push the GitLab image after having created my test users. So: how should I persist them? One way would be to create them on startup using the API after each new deployment, but this is quite slow/cumbersome. 回答1: As you said, it's not going to be as easy as committing and pushing a

问题 Using docker-compose I'm attempting to create a shared volume that two of my services can both use. I have the following in my docker-compose.yml version: '2' volumes: bundler: driver: local sidekiq: build: . volumes_from: - bundler:/.bundle web: build: . volumes_from: - bundler:/.bundle This however doesn't work and gives me: ERROR: Service "sidekiq" mounts volumes from "bundler", which is not the name of a service or container. What is the correct way of doing this using docker-compose? 回答1

问题 I am working on a web application that requires few microservices like a URL shorter, mailer, analytics, etc... Each of these services are implemented as REST api so they can talk to each other. Each of these services have a docker-compose.yml file and use containers like nginx, php, mysql, etc… I want these to work as a single system. I don’t want to expose these REST apis to anyone outside of the docker network My question is how can I combine multiple docker-compose.yml files from each

问题 I have set up two new projects in Visual Studio using the Docker tooling. The first is a asp.net site running against a Linux container. The second is an asp.net site running against a Windows container. In the former, I can ping hostnames (ex: google.com) and it resolves just fine. However, when running the windows container I cannot do the same thing. I am running a custom network so that I can ensure the container starts up on the subnet I want: docker network create --driver=nat --subnet

问题 This is docker in docker scenario. Below is the corresponding code in Dockerfile that has docker client installed: FROM jenkins/jenkins:2.190.2 ENV DEBIAN_FRONTEND=noninteractive # Official Jenkins image does not include sudo, change to root user USER root # Used to set the docker group ID # Set to 497 by default, which is the groupID used by AWS Linux ECS instance ARG DOCKER_GID=497 # Create Docker Group with GID # Set default value of 497 if DOCKER_GID set to blank string by Docker compose

问题 I am setting up 2 VPC on GCP, I setup kubeadm on each, let's call them kubemaster and kubenode1. So I ran kubeadm on kubemaster and kubenode1 which : kubeadm init on kubemaster kubeadm join on kubenode1 When I was trying to kubectl apply -f (a deployment which contains a pod with simple webapps inside) and kubectl apply -f (a NodePort type of Service which target the deployment port) After that I simply access the webapps from my browser (on my local machine not on GCP), it just does not work

问题 When I run the following command, I expect the exit code to be 0 since my combined container runs a test that successfully exits with an exit code of 0. docker-compose up --build --exit-code-from combined Unfortunately, I consistently receive an exit code of 137 even when the tests in my combined container run successfully and I exit that container with an exit code of 0 (more details on how that happens are specified below). Below is my docker-compose version: docker-compose version 1.25.0,

问题 I have a raspberry pi and I have installed dockers in it. I have made a python script to read gpio status in it. So when I run the below command sudo docker run -it --device /dev/gpiomem app-image It runs perfectly and shows the gpio status. Now I have created a docker-compose.yml file as I want to deploy this app.py to the swarm cluster which I have created. Below is the content of docker-compose.yml version: "3" services: app: image: app-image deploy: mode: global restart: always privileged