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
Cannot start service proxy: driver failed programming external connectivity on endpoint #1003
Comments
@joe-westcott I just now came across the same error with beta 45 of Lando and Docker 17.12.0-c-win47. I don't think this problem is connected to #1001. |
FWIW, with beta47 on both Ubuntu and Arch Linux, I solved this by restarting my host machine. No amount of destroying apps or removing docker containers or deleting Lando cache made a difference, as had helped in previous versions. But after a reboot, all was well :) |
Same for me, only a reboot fixed it |
seems to be the same issue: #1754 |
Seems to be also be a problem if you have any docksal projects running on your docker instance.
If I restart my host machine and start my lando project first, it seems like I can boot up a docksal project afterwards, but never before, making me think there is an issue with the corrective action script, I think we need to flip ports from 443 to 80 if it's already in use. |
We already do this and it works fairly well which any Pantheon Localdev
user can attest to.
This won’t work however if you’ve locked down all the fallback ports on
your machine.
…On Fri, Mar 27, 2020 at 2:13 AM Aaron Christian ***@***.***> wrote:
Seems to be a problem if you have any docksal projects running, and then
you add a lando one to the mix.
Error starting userland proxy: listen tcp 0.0.0.0:443: bind: address
already in use
If I restart my host machine and start my lando project first, it seems
like I can boot up a docksal project afterwards, but *never* before,
making me think there is an issue with the corrective action script, I
think we need to flip ports from 443 to 80 if it's already in use.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#1003 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFOFUCT3XMWUGXFHCQWHKDRJQ72BANCNFSM4FCPVM6A>
.
|
I have faced the issue and found that docksal is using the same port. Stop docksal docker made the issue resolved. |
Hi, this seems related but not exactly the same as issue #1001. Getting this error:
Cannot start service proxy: driver failed programming external connectivity on endpoint landoproxyhyperion5000gandalfedition_proxy_1 (05090b6540fc7e467d0439fcc727fec87215a772154be62651fc1efdfbacc573): Error starting userland proxy: mkdir /port/tcp:0.0.0.0:58086:tcp:172.19.0.2:8080: input/output error
Bug Report
Lando v3.0.0-beta.46 on Windows 10 Professional
Docker 18.03.1-ce-win65 (17513)
.lando.yml
Tell us about the command you were running
lando start
Tell us about the error you got
Complete verbose log here:
https://www.dropbox.com/s/xsu8bro1ji4hbx7/lando-46-error-starting-userland-proxy-verbose.txt?dl=0
Tell us generally about your bug
Lando .45 wasn't working for me due to blocker issue #990 , so I upgraded from Lando .45 to Lando .46.
Then I:
lando init
successfully.lando start
, and the stream of new errors began.After that, I:
lando init
lando start
, and got the exact same errors.lando rebuild
, and got the exact same errors.Tell us more
Does this bug prevent you from using lando?
YES! I can't get any work done, and downgrading to Lando .45 isn't an option due to the blocker bug in that version -- issue #990.
Thanks for your help with this bug.
The text was updated successfully, but these errors were encountered: