Compose: I am having this "Encountered errors while bringing up the project." error

Created on 19 Oct 2017  路  12Comments  路  Source: docker/compose

when $ docker-compose up it returns

Starting df33a29fc6ee_df33a29fc6ee_adaptive-admin_mariadb ...
Starting df33a29fc6ee_df33a29fc6ee_adaptive-admin_mariadb ... error

Docker Version

Client:
 Version:      17.07.0-ce
 API version:  1.31
 Go version:   go1.8.3
 Git commit:   8784753
 Built:        Tue Aug 29 17:41:05 2017
 OS/Arch:      windows/amd64

Server:
 Version:      17.09.0-ce
 API version:  1.32 (minimum version 1.12)
 Go version:   go1.8.3
 Git commit:   afdb6d4
 Built:        Tue Sep 26 22:45:38 2017
 OS/Arch:      linux/amd64
 Experimental: false

on $ docker-compose --verbose up

compose.parallel.feed_queue: Pending: set([])
Starting df33a29fc6ee_df33a29fc6ee_adaptive-admin_mariadb ... error
compose.parallel.feed_queue: Pending: set([])

ERROR: compose.cli.main.main: Encountered errors while bringing up the project.

Most helpful comment

Does running docker-compose down solve the issue?

All 12 comments

Does running docker-compose down solve the issue?

No, I figured out I have to install composer to solve the issue.

@shin- that command line you wrote there solved my issue!! man.. I searched so many places couldn't get my issue solved, I got say THANK YOU bro!! thanks so much.

docker-compose down --> worked for me..
Thanks

That works for me. Thank you

None of the above worked for me.
Environment:

  • Ubuntu 16.04
  • Docker version 18.09.0, build 4d60db4
  • docker-compose version 1.18.0, build 8dd22a9

some of the time if you forgot to include any package in requirement.txt gives u package oriented failure error.

That works for me Thinks!

try with it:

sudo pkill mysql
sudo pkill mysqld
docker-compose down
docker-compose up

Does running docker-compose down solve the issue?

Thank you this worked for me as well. My dev and prod environments were running correctly but local was giving the error.
Running docker-compose -f local.yml down solved the error for me.

I encountered an installation issue I don't know how to solve a problem

Creating azuracast_nginx_proxy_1 ... error

ERROR: for azuracast_nginx_proxy_1 Cannot start service nginx_proxy: driver failed programming external connectivity on endpoint azuracast_nginx_proxy_1 (1252b820c80ae8a6f188978baf4f99155feb9430d4330db28c991dfd1f8e96ab): Error starting userland proxy: listen tcp 0.0.0.0:80: listen: address already in use

ERROR: for nginx_proxy Cannot start service nginx_proxy: driver failed programming external connectivity on endpoint azuracast_nginx_proxy_1 (1252b820c80ae8a6f188978baf4f99155feb9430d4330db28c991dfd1f8e96ab): Error starting userland proxy: listen tcp 0.0.0.0:80: listen: address already in use
ERROR: Encountered errors while bringing up the project.
root@radio:/var/azuracast#

In my case I tried to start a webserver (nginx for let's encrypt) and got the error:
Bind for 0.0.0.0:80 failed: port is already allocated

The reason was, that another docker project was running nginx (thus the port was really already in use)

Solution was to use docker ps to find the running container/s and stop it/them: docker stop CONTAINER_ID

Was this page helpful?
0 / 5 - 0 ratings