-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am having this "Encountered errors while bringing up the project." error #5286
Comments
Does running |
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.. |
That works for me. Thank you |
None of the above worked for me.
|
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 |
Thank you this worked for me as well. My dev and prod environments were running correctly but local was giving the error. |
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 |
In my case I tried to start a webserver (nginx for let's encrypt) and got the error: The reason was, that another docker project was running nginx (thus the port was really already in use) Solution was to use |
$ make start ERROR: for reaction_mongo_1 Cannot start service mongo: driver failed programming external connectivity on endpoint reaction_mongo_1 (5b5f99016cba3d432aab21eb5119446e6b6c47755f36deb371ea579e72a1968d): Error starting userland proxy: listen tcp 0.0.0.0:27017: bind: address already in use ERROR: for mongo Cannot start service mongo: driver failed programming external connectivity on endpoint reaction_mongo_1 (5b5f99016cba3d432aab21eb5119446e6b6c47755f36deb371ea579e72a1968d): Error starting userland proxy: listen tcp 0.0.0.0:27017: bind: address already in use |
I LOVE SO MUCH! |
I love YOU so much bro thanks! I was having a problem with postgres and I try sudo pkill postgres and docker-compose down and works |
Hello !, I got the error like blelow one
I'm using ubuntu 18.04 and docker Version: 20.10.10. can you please suuggest for this issue? |
مرحبا بك بي ما أسعدك
Le sam. 30 oct. 2021 à 14:18, sathishkurichy ***@***.***> a
écrit :
… Hello !,
I got the error like blelow one
Digest: sha256:58132ff3162cf9ecc8e2042c77b2ec46f6024c35e83bda3cabde76437406f8ac
Status: Downloaded newer image for redis:alpine
Creating getground_workspace_1 ...
Creating getground_workspace_1 ... error
Creating getground_mysql_1 ...
Creating getground_php-fpm_1 ...
Creating getground_redis_1 ...
Creating getground_web_1 ... done
Creating getground_mysql_1 ... done
Creating getground_php-fpm_1 ... done
Creating getground_redis_1 ... done
ERROR: for workspace Cannot start service workspace: driver failed programming external connectivity on endpoint getground_workspace_1 (e033dd78aefe4217b11055f1ebf424df8f2428c87a14f8a459911eb611c34285): Error starting userland proxy: listen tcp4 0.0.0.0:3000: bind: address already in use
ERROR: Encountered errors while bringing up the project.
I'm using ubuntu 18.04 and docker Version: 20.10.10. can you please
suuggest for this issue?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5286 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APXNIFXRM7AASW3RPLAQRYDUJPWC7ANCNFSM4D723PGA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
it avoids the issue. The point with automatic tests is, well... automation. I have to run docker-compose down after every time I run my test . Clearly I am missing something. |
This worked for me |
مرحبا
Le ven. 4 nov. 2022 à 15:58, camilabmc ***@***.***> a écrit :
… try with it:
sudo pkill mysql sudo pkill mysqld docker-compose down docker-compose up
This worked for me
—
Reply to this email directly, view it on GitHub
<#5286 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APXNIFRC5R4HL2J23MURCOTWGUQABANCNFSM4D723PGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
when
$ docker-compose up
it returnsDocker Version
on $ docker-compose --verbose up
The text was updated successfully, but these errors were encountered: