search

arunoda / meteor-up-legacy

Production Quality Meteor Deployments
MIT License
2.26k stars 394 forks source link

Mupx: docker: Error response from daemon: driver failed programming external connectivity on endpoint cbv2... Bind for 0.0.0.0:9000 failed: port is already allocated. #1072

Open lpatmo opened 8 years ago

lpatmo commented 8 years ago

When trying to deploy I got this error:

Meteor Up: Production Quality Meteor Deployments
------------------------------------------------
Configuration file : mup.json
Settings file      : settings.json

“ Checkout Kadira!
  It's the best way to monitor performance of your app.
  Visit: https://kadira.io/mup ”

Meteor app path    : /Users/lindapeng/Desktop/lindaprojects/stage
Using buildOptions : {}

Started TaskList: Deploy app 'cbv2' (linux)
[192.241.203.23] - Uploading bundle
[192.241.203.23] - Uploading bundle: SUCCESS
[192.241.203.23] - Sending environment variables
[192.241.203.23] - Sending environment variables: SUCCESS
[192.241.203.23] - Initializing start script
[192.241.203.23] - Initializing start script: SUCCESS
[192.241.203.23] - Invoking deployment process
[192.241.203.23] x Invoking deployment process: FAILED

    -----------------------------------STDERR-----------------------------------
    Error response from daemon: No such container: cbv2
    Error response from daemon: No such container: cbv2-frontend
    docker: Error response from daemon: driver failed programming external connectivity on endpoint cbv2 (4f34a8a9022ad350c63ec184c87088d8eab521b4d47dd971422f2d42411e268b): Bind for 0.0.0.0:9000 failed: port is already allocated.
    -----------------------------------STDOUT-----------------------------------
    base: Pulling from meteorhacks/meteord
    4d690fa98655: Already exists
    a3ed95caeb02: Already exists
    0638f01c6191: Already exists
    086f3bb36259: Already exists
    Digest: sha256:684021facd5847f6a4ee2f0095fd26b4d7f5af2b776150531914d43fd0eb889b
    Status: Image is up to date for meteorhacks/meteord:base
    a146089504896c1a7f1aa1ae2cb04c741c6c8379c9ae8a4a091a90ae5cb8a67e
    ----------------------------------------------------------------------------

Previously, I'd misguidedly rm -rf'ed my /opt/ folder after reading through the advice on https://github.com/arunoda/meteor-up/issues/651 in an attempt to get SSL working. Not sure if it's related.

DerMarcus commented 8 years ago

Hi, yes it is related. You removed the necessary folder. Just try to remove the still running docker container:

  1. docker info - check if container is still running
  2. docker stop try to stop it. If you cant stop it, executed step 3. and restart the docker daemon, because it will not started anymore.
  3. docker rm - for removing the app. Sometimes docker rm -link is also necessary.