docker-compose

Terraform: Deploying a Docker Compose app on EKS/ECS

℡╲_俬逩灬. 提交于 2020-05-14 19:46:50
问题 TL;DR I use an open-source server application running on Docker Compose . It has a few services, including PostgreSQL DB and Redis. How can I best deploy this application to AWS in full IaC with Terraform? Solutions so far 1. AWS ecs-cli ecs-cli now supports sending docker compose configs in Amazon ECS. However, I do not think it could be integrated with the Terraform workflow (which is maybe not a big fuss). What I know for sure is that ecs-cli is not supported in CloudFormation , as per

Docker container shuts down giving 'data directory has wrong ownership' error when executed in windows 10

两盒软妹~` 提交于 2020-05-14 16:33:26
问题 I have my docker installed in Windows. I am trying to install this application. It has given me the following docker-compose.yml file: version: '2' services: web: build: context: . dockerfile: Dockerfile-nginx ports: - "8085:80" networks: - attendizenet volumes: - .:/usr/share/nginx/html/attendize depends_on: - php php: build: context: . dockerfile: Dockerfile-php depends_on: - db - maildev - redis volumes: - .:/usr/share/nginx/html/attendize networks: - attendizenet php-worker: build:

docker-compose restart interval

…衆ロ難τιáo~ 提交于 2020-05-13 04:33:05
问题 I have a docker-compose.yml file with a following: services: kafka_listener: build: . command: bundle exec ./kafka foreground restart: always # other services Then I start containers with: docker-compose up -d On my amazon instance kafka-server (for example) fails to start sometimes, so ./kafka foregound script fails. When typing docker ps I see a message: Restarting (1) 11 minutes ago . I thought docker should restart failed container instantly, but it seems it doesn't. After all, container

Prometheus (in Docker container) Cannot Scrape Target on Host

戏子无情 提交于 2020-05-12 23:28:43
问题 Prometheus running inside a docker container ( version 18.09.2, build 6247962 , docker-compose.xml below) and the scrape target is on localhost:8000 which is created by a Python 3 script. Error obtained for the failed scrape target ( localhost:9090/targets ) is Get http://127.0.0.1:8000/metrics: dial tcp 127.0.0.1:8000: getsockopt: connection refused Question: Why is Prometheus in the docker container unable to scrape the target which is running on the host computer (Mac OS X)? How can we get

Prometheus (in Docker container) Cannot Scrape Target on Host

我的未来我决定 提交于 2020-05-12 23:28:39
问题 Prometheus running inside a docker container ( version 18.09.2, build 6247962 , docker-compose.xml below) and the scrape target is on localhost:8000 which is created by a Python 3 script. Error obtained for the failed scrape target ( localhost:9090/targets ) is Get http://127.0.0.1:8000/metrics: dial tcp 127.0.0.1:8000: getsockopt: connection refused Question: Why is Prometheus in the docker container unable to scrape the target which is running on the host computer (Mac OS X)? How can we get

Prometheus (in Docker container) Cannot Scrape Target on Host

安稳与你 提交于 2020-05-12 23:26:58
问题 Prometheus running inside a docker container ( version 18.09.2, build 6247962 , docker-compose.xml below) and the scrape target is on localhost:8000 which is created by a Python 3 script. Error obtained for the failed scrape target ( localhost:9090/targets ) is Get http://127.0.0.1:8000/metrics: dial tcp 127.0.0.1:8000: getsockopt: connection refused Question: Why is Prometheus in the docker container unable to scrape the target which is running on the host computer (Mac OS X)? How can we get

Cannot mount Config directory in Nextcloud Docker container

痴心易碎 提交于 2020-05-12 08:07:26
问题 I'm trying to create a custom Nextcloud config locally, then have the ability to mount it to the appropriate folder using volumes as defined here: https://github.com/nextcloud/docker#persistent-data. All the volume mounts work except for the config mount... Why is that being treated differently here? Steps to reproduce 0) Enter a new/emptry directory (containing no sub-directories or additional files). 1) Create a docker-compose.yml file containing only the below contents: version: "3.4"

Installed gems not found by bundler when BUNDLE_PATH changed with Docker

给你一囗甜甜゛ 提交于 2020-05-11 05:38:07
问题 I'm using docker to develop a rails application. The docker file looks like this: FROM ruby:1.9.3 RUN apt-get update -qq && apt-get install -y build-essential libpq-dev vim ENV APP_HOME /next-reg RUN mkdir $APP_HOME WORKDIR $APP_HOME ENV BUNDLE_PATH /box ADD . $APP_HOME RUN gem install gem1.gem gem2.gem COPY Gemfile Gemfile COPY Gemfile.lock Gemfile.lock RUN bundle install As you can see I change the bundle_path , this is because of an article showing how we can persist gem downloads. So that

Installed gems not found by bundler when BUNDLE_PATH changed with Docker

痴心易碎 提交于 2020-05-11 05:37:07
问题 I'm using docker to develop a rails application. The docker file looks like this: FROM ruby:1.9.3 RUN apt-get update -qq && apt-get install -y build-essential libpq-dev vim ENV APP_HOME /next-reg RUN mkdir $APP_HOME WORKDIR $APP_HOME ENV BUNDLE_PATH /box ADD . $APP_HOME RUN gem install gem1.gem gem2.gem COPY Gemfile Gemfile COPY Gemfile.lock Gemfile.lock RUN bundle install As you can see I change the bundle_path , this is because of an article showing how we can persist gem downloads. So that

Installed gems not found by bundler when BUNDLE_PATH changed with Docker

时光毁灭记忆、已成空白 提交于 2020-05-11 05:36:14
问题 I'm using docker to develop a rails application. The docker file looks like this: FROM ruby:1.9.3 RUN apt-get update -qq && apt-get install -y build-essential libpq-dev vim ENV APP_HOME /next-reg RUN mkdir $APP_HOME WORKDIR $APP_HOME ENV BUNDLE_PATH /box ADD . $APP_HOME RUN gem install gem1.gem gem2.gem COPY Gemfile Gemfile COPY Gemfile.lock Gemfile.lock RUN bundle install As you can see I change the bundle_path , this is because of an article showing how we can persist gem downloads. So that