docker-compose

问题 Closed . This question needs details or clarity. It is not currently accepting answers. Want to improve this question? Add details and clarify the problem by editing this post. Closed 8 days ago . Improve this question I have a Nuxt Js app running under docker . Everything is running fine i can access the app on http://172.20.0.3:3000/. However i would like to access the app via http://external_ip. How can i do this? 来源： https://stackoverflow.com/questions/65338786/how-can-i-make-docker-app

问题 Closed . This question needs details or clarity. It is not currently accepting answers. Want to improve this question? Add details and clarify the problem by editing this post. Closed 8 days ago . Improve this question I have a Nuxt Js app running under docker . Everything is running fine i can access the app on http://172.20.0.3:3000/. However i would like to access the app via http://external_ip. How can i do this? 来源： https://stackoverflow.com/questions/65338786/how-can-i-make-docker-app

问题 I am new to docker and having a simple DW(dropwizard) application that connects to elasticsearch, Which is already running in docker using the docker-compose.yml, which has the following content. Docker-compose.yml for elasticsearch version: '2.2' services: elasticsearch: image: docker.elastic.co/elasticsearch/elasticsearch:7.6.0 container_name: elasticsearch environment: - xpack.security.enabled=false - discovery.type=single-node ports: - 8200:9200 - 8300:9300 volumes: elasticsearch-data:

问题 I am trying to create a wrapper container to build and run a set of containers using a docker-compose I cannot modify. The docker-compose mounts several volumes, but when starting the docker-compose from inside of the wrapper docker, the volumes are still mounted from the host since the docker .sock is volume mounted to be the host's docker.sock. I would like to not have to use full docker-in-docker due to all the problems associated with it outlined in jpetazzo's article. I would also like

问题 I think I'm going to go crazy. I've searched all over and can't seem to find a working solution both here on Stack, GitHub and other far reaches of the interwebs. On this particular project, running docker-compose build is taking FOREVER . It didn't use to be this way, and on other projects that use Docker, it's not an issue at all. And by forever... I'm talking around 10-15 minute build times when it used to only take around 2 minutes tops. I had two separate coworkers DL the same repo (one

问题 I think I'm going to go crazy. I've searched all over and can't seem to find a working solution both here on Stack, GitHub and other far reaches of the interwebs. On this particular project, running docker-compose build is taking FOREVER . It didn't use to be this way, and on other projects that use Docker, it's not an issue at all. And by forever... I'm talking around 10-15 minute build times when it used to only take around 2 minutes tops. I had two separate coworkers DL the same repo (one

问题 I think I'm going to go crazy. I've searched all over and can't seem to find a working solution both here on Stack, GitHub and other far reaches of the interwebs. On this particular project, running docker-compose build is taking FOREVER . It didn't use to be this way, and on other projects that use Docker, it's not an issue at all. And by forever... I'm talking around 10-15 minute build times when it used to only take around 2 minutes tops. I had two separate coworkers DL the same repo (one

问题 I run these docker commands locally to copy a file to a volume, this works fine: docker container create --name temp_container -v temp_vol:/target hello-world docker cp somefile.txt temp_container:/target/. Now I want to do the same, but with volumes located in Azure. I have an image azureimage that I pushed and it's located in Azure, and I need to access from the container a volume with a file that I have in my local disk. I can create the volume in an Azure context like so: docker context

问题 I run these docker commands locally to copy a file to a volume, this works fine: docker container create --name temp_container -v temp_vol:/target hello-world docker cp somefile.txt temp_container:/target/. Now I want to do the same, but with volumes located in Azure. I have an image azureimage that I pushed and it's located in Azure, and I need to access from the container a volume with a file that I have in my local disk. I can create the volume in an Azure context like so: docker context

问题 My docker-compose.yml : solr: image: solr:8.6.2 container_name: myproject-solr ports: - "8983:8983" volumes: - ./data/solr:/var/solr/data networks: static-network: ipv4_address: 172.20.1.42 After bringing up the docker with docker-compose up -d --build , the solr container is down and the log ( docker logs myproject-solr ) shows this: Copying solr.xml cp: cannot create regular file '/var/solr/data/solr.xml': Permission denied I've noticed that if I give full permissions on my machine to the