docker-compose

How to mount docker volume in Azure Web App for containers?

元气小坏坏 提交于 2020-12-31 17:53:09
问题 I'm trying to run KrakenD image in Azure App Service. KrakenD requires json config file krakend.json to be put into /etc/krakend/ ( KrakenD image is based on Linux Alpine ) I created Web App for containers with the following docker-compose file: version: "3" services: krakend: image: devopsfaith/krakend:latest volumes: - ${WEBAPP_STORAGE_HOME}/site/krakend:/etc/krakend ports: - "8080:8080" restart: always Added storage account with a blob container where uploaded sample kraken.json file In

OSError: Can not read file in context: \\?\C:\project\.gradle\6.6.1\executionHistory\executionHistory.lock

帅比萌擦擦* 提交于 2020-12-31 05:40:54
问题 I have a Gradle project and I'm using docker in this project. When I execute the command gradlew integrationTestDocker , I get the error below. OSError: Can not read file in context: \\?\C:\project\.gradle\6.6.1\executionHistory\executionHistory.lock 回答1: That was reported before in Oct. 2018 (issue 7043) and Nov. 2019 (issue 11520) In both cases, the suggestion was to add .gradle to the .dockerignore , in order to make sure it is not part of the docker build context. Plus this comment: After

OSError: Can not read file in context: \\?\C:\project\.gradle\6.6.1\executionHistory\executionHistory.lock

陌路散爱 提交于 2020-12-31 05:39:33
问题 I have a Gradle project and I'm using docker in this project. When I execute the command gradlew integrationTestDocker , I get the error below. OSError: Can not read file in context: \\?\C:\project\.gradle\6.6.1\executionHistory\executionHistory.lock 回答1: That was reported before in Oct. 2018 (issue 7043) and Nov. 2019 (issue 11520) In both cases, the suggestion was to add .gradle to the .dockerignore , in order to make sure it is not part of the docker build context. Plus this comment: After

Docker build using volumes at build time

社会主义新天地 提交于 2020-12-31 04:34:35
问题 Is there a way to use external volumes during the docker image build ? I have a situation where I would like to use a configuration inside a external volume during the docker image build time. Is that possible? 回答1: If by 'docker image build' you mean running a single 'docker build ...' command: no, there is no way to do that (at least, not in the most recent documentation that I have read). However, nothing prevents you from performing the step that needs the external volume using direct

Docker build using volumes at build time

此生再无相见时 提交于 2020-12-31 04:32:13
问题 Is there a way to use external volumes during the docker image build ? I have a situation where I would like to use a configuration inside a external volume during the docker image build time. Is that possible? 回答1: If by 'docker image build' you mean running a single 'docker build ...' command: no, there is no way to do that (at least, not in the most recent documentation that I have read). However, nothing prevents you from performing the step that needs the external volume using direct

GraphQL ERESOLVE unable to resolve dependency tree when building my docker container

╄→гoц情女王★ 提交于 2020-12-30 08:15:20
问题 Here are my files. Here is I think the core of the problem. Could not resolve dependency: npm ERR! peer graphql@"^0.12.0 || ^0.13.0 || ^14.0.0" from graphql-middleware@4.0.2 docker-compose.yml version: '3.7' services: apollo: container_name: apollo build: context: . dockerfile: Dockerfile environment: - NODE_ENV=development volumes: - '.:/app' - '/app/node_modules' ports: - 4000:4000 restart: always Dockerfile # Use the official image as a parent image. FROM node:current-slim # Set the

GraphQL ERESOLVE unable to resolve dependency tree when building my docker container

这一生的挚爱 提交于 2020-12-30 08:14:31
问题 Here are my files. Here is I think the core of the problem. Could not resolve dependency: npm ERR! peer graphql@"^0.12.0 || ^0.13.0 || ^14.0.0" from graphql-middleware@4.0.2 docker-compose.yml version: '3.7' services: apollo: container_name: apollo build: context: . dockerfile: Dockerfile environment: - NODE_ENV=development volumes: - '.:/app' - '/app/node_modules' ports: - 4000:4000 restart: always Dockerfile # Use the official image as a parent image. FROM node:current-slim # Set the

GraphQL ERESOLVE unable to resolve dependency tree when building my docker container

好久不见. 提交于 2020-12-30 08:13:25
问题 Here are my files. Here is I think the core of the problem. Could not resolve dependency: npm ERR! peer graphql@"^0.12.0 || ^0.13.0 || ^14.0.0" from graphql-middleware@4.0.2 docker-compose.yml version: '3.7' services: apollo: container_name: apollo build: context: . dockerfile: Dockerfile environment: - NODE_ENV=development volumes: - '.:/app' - '/app/node_modules' ports: - 4000:4000 restart: always Dockerfile # Use the official image as a parent image. FROM node:current-slim # Set the

GraphQL ERESOLVE unable to resolve dependency tree when building my docker container

北城以北 提交于 2020-12-30 08:13:15
问题 Here are my files. Here is I think the core of the problem. Could not resolve dependency: npm ERR! peer graphql@"^0.12.0 || ^0.13.0 || ^14.0.0" from graphql-middleware@4.0.2 docker-compose.yml version: '3.7' services: apollo: container_name: apollo build: context: . dockerfile: Dockerfile environment: - NODE_ENV=development volumes: - '.:/app' - '/app/node_modules' ports: - 4000:4000 restart: always Dockerfile # Use the official image as a parent image. FROM node:current-slim # Set the

Fallback for environment variables with docker-compose

允我心安 提交于 2020-12-30 06:57:52
问题 Given the following configuration: mysql: environment: MY_MYSQL_PORT: image: mysql ports: - "${MY_MYSQL_PORT}:3306" There's a way to provide a fallback value for MY_MYSQL_PORT without relying on wrapper scripts? I already tested like bash ${MY_MYSQL_PORT-3306} but it doesn't work. 回答1: They implemented that feature with compose 1.9 release: Added support for shell-style inline defaults in variable interpolation. The supported forms are ${FOO-default} (fall back if FOO is unset) and ${FOO: