ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
I have a docker-compose file and a Dockerfile. MySQL is installed properly. I have set MYSQL_ROOT_PASSWORD . But when trying to access mysql db, getting the error - Access denied. I have read the other threads of this site, but couldn't get that much help. :( Here is my docker-compose file: version: '3' volumes: db_data: {} services: db: build: context: . do
I wanted to translate this docker CLI command (from smallstep/step-ca ) into a docker-compose.yml file to run with docker compose (version 2): docker run -d -v step:/home/step \ -p 9000:9000 \ -e "DOCKER_STEPCA_INIT_NAME=Smallstep" \ -e "DOCKER_STEPCA_INIT_DNS_NAMES=localhost,$(hostname -f)" \ smallstep/step-ca This command successfully starts the container.
In the first line of the docker-compose.yml file we specify a version: version: '3.9' What exactly does this mean?! After installing the latest version, I tried the following in my Windows 10 cmd : docker-compose --version and the output was: Docker Compose version v2.17.2 so how is it that we type 3.9 in the first line?!
I might have a bit of a messed Docker installation on my Mac.. At first I installed Docker desktop but then running it I learned that as I'm on an older Mac I had to install VirtualBox so I did following these steps: enable writing on the /usr/local/bin folder for user sudo chown -R $(whoami) /usr/local/bin install Docker-Machine base=https://github.com/dock
init container is a great feature in Kubernetes and I wonder whether docker-compose supports it? it allows me to run some command before launch the main application. I come cross this PR https://github.com/docker/compose-cli/issues/1499 which mentions to support init container. But I can't find related doc in their reference.
I am building a django-react site and suddenly my docker-compose no longer builds despite any changes to requirements or image versions. My requirements.txt looks as follows: Django>=3.2.4,<4.0 djangorestframework>=3.12.4,<3.14.0 djangorestframework-simplejwt>=4.8.0,<5.3.0 psycopg2>=2.8.6,<2.9 drf-spectacular>=0.15.1,<0.30 djang
I have a large understanding problem when it comes to docker-compose, Dockerfile and how GCP's service Cloud Run works. This makes me unable to advance in a project I have and I am litteraly out of things to try. I have a docker-compose.yml file with the following content: version: '2' services: # The Application app: container_name: laravel_app build: conte
I have a simple frontend and backend app. And I have a docker-compose file but it's inside frontend folder. So when I run it both frontend and backend containers are under frontend container (it takes name of the folder) how can I rename this main container? I am using version 3.9 version: "3.9" services: be_service: container_name: backend build: context: .
I was building docker image using the command docker-compose -f "docker-compose.yml" up -d --build But it returns me an error ERROR: 2 matches found based on name: network officeconverter_default is ambiguous This is a bit clear that in my machine there are two networks with the same name trying to exists. Question is how to remove the networks from docker n
commented · 28 Jan 2021, 08:10 UTC
docker
homebrew