I'm doing this docker tutorial, but I keep encounter an error: Image of CMD.
and when i check my file:
Image of Compose-file
does anyone what i did wrong?
I am main follow the instructions on https://docs.docker.com/get-started/08_using_compose/
mysql should be on the level of app
indentation matters here..
you are adding mysql as sub comoponent of app service , but it should be on same level of app , as mysql is also one service
Related
This might look similar to this existing solution but I have tried all the solutions mentioned there and none seems to resolve my issue.
I have created a docker compose file , Docker-Compose-V3.yml.
On running docker-compose -f docker-compose-v3.yml up I am able to successfully spin up the grid network.
When I am trying to scale my chrome nodes using docker-compose up --scale chrome = 5 I am getting no configuration file provided: not found error message
I have tried following solutions from the existing answer linked but to no avail
Made sure I am in correct directory where the docker compose file is present
Checked the extension of yml file and cross checked the folder option settings
I am unable to understand that why is docker able to identify the compose file when asked to spin up the grid but fails to do so when I am trying to scale up the services.
I know that another possible way I can do it is using docker swarm which I came to know of while scrolling through docker documentation but would like to understand why this isn't working.
Needless to say but I have just started exploring the docker world and would appreciate any help in being pointed towards the existing documentation/answers that would resolve my problem
Im following this quickstart guide: https://github.com/shopware/platform#quickstart--installation
Everything worked until I tried to start the docker container via ./psh.phar docker:start in the cmd. The docker hub starts but no container. Im not getting any errors. Can someone help me?
Not quite an answer to your question, but I & Shopware recommends using https://dockware.io for the "quick start" of any of your docker work. Here is a link from their tutorial: https://developer.shopware.com/docs/guides/installation/dockware
I have used those images extensively & they boot up without much modifications needed.
I have docker-compose.yml
volumes:
- D:/Docker/config:/config
- D:/Downloads:/downloads
I can do this with docker-compose up without any issue
But in portainer stack, I got an error
Deployment error
failed to deploy a stack: Named volume "D:/Docker/config:/config" is used in service "test" but no declaration was found in the volumes section. : exit status 1
Basically I want to map my host folder D:/Docker/config. How do I do this in portainer?
I spent a long time figuring this out
So in Docker-Compose, on Windows running Docker Desktop in WSL2 mode when entering a mount point for a Bind Mount you have to format it
- /mnt/DRIVE-LETTER/directory/to/location:/container/path
An example would be
- /mnt/k/docker/tv/xteve/config:/home/xteve/config
You also have the option of using relative paths from where the Compose file is located but with Portainer that isn't an option. I know, I tried everything I could think of. Then I was looking at tutorials & I saw the same thing #warheat1990 posted here & experimented with that.
Portainer tells you to paste your Docker-Compose, but the paths are different. The paths inside Portainer will not work & be ignored or placed somewhere you can't get to them from windows, unless you remove the "/mnt" & start with the drive letter
- /DRIVE-LETTER/directory/to/location:/container/path
An example would be
- /k/docker/tv/xteve/config:/home/xteve/config
I tested it & outside of Portainer without the "/mnt" it fails, but within Portainer it can't be there. So far I'm fairly confident that there is no way to do it that works for both. Which is super annoying because Portainer makes it easy to paste your Compose or actually import the file, but then you must edit it, just nobody tells you that...
Hope that helps
use /d/Downloads to make it work, thanks to #xerx593
edit : came here about the same question, and forgot the question was for portainer. This answer below worked in docker compose in windows.
Not sure how helpful that is but as I was trying to deploy Filerun in docker desktop windows, I ran into that issue myself.
Goal was to have my containers data in one place on a windows folder but Filerun files were a different drive.
I fumbled A LOT but what worked for me in the end with docker compose :
volumes:
- D:\myfolder:/mnt/myfolder
- ./filerun/html:/var/www/html
- ./filerun/user-files:/user-files # (default, could be pointed directly to mnt)
The ./filerun define a relative path to where the docker compose yml is stored and executed so that I have persistence in my windows folder there even when removing a compose (this is not intended for intensive prodiction stuff).
And my files were accessible in Filerun through /mnt/myfolder.
Not sure if docker desktop has been updated on that since the previous answer was given.
I'm trying to setup Elastic Enterprise Search and App Search using Docker. So far I managed to install Elastic Search and Kibana using Docker on Centos 7. Right now, I want to establish a connection with GitHub, for which I'll need Enterprise search. I opened the page, but it's prompting to "Add your workspace Search host URL to your Kibana Configuration - enterpriseSearch.host: 'http://localhost:3002'
I didn't quite understand on how to do that. I'm stuck with this. Can anyone please provide some step-by-step instructions?
As per the ElasticSearch documentation:
enterpriseSearch.host | The URL of your Enterprise Search instance
I am looking at this step as well, to configure the kibana docker container you can either pass environment variables to the docker container as you run it (usually by making use of a docker-compose.yml file), or you can pass it a kibana.yml file on the command line.
Reference:
https://www.elastic.co/guide/en/kibana/current/docker.html#configuring-kibana-docker
It's worth noting if you are running elasticsearch on docker following the same instructions as me you have not opened up port 3002 when launching that which may need to be completed by changing the run code to include 3002:3002.
I am running Confluent Platform all-in-one docker-compose file on my Mac by the steps described in this confluent doc.
However, when every container is up (checked using docker-compose ps), I cannot reach the Control Center web interface at http://localhost:9021/. I waited a lot, so it could not be an issue with starting up.
I also checked the url with IP of the docker image plus port 9021 - still unable to connect.
Why could that be, and how can I fix that?
I was also facing same problem and was able to fix it by using .arm64 based images as I was having mac with Apple M1 Pro chipset. So, in the default docker-compose.yml image names I just appended .arm64 at the end and it started working for me.
I hope it helps for someone in future.