search

arunoda / meteor-up-legacy

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

mupx x Invoking deployment process: FAILED - Error response from daemon: no such id: #711

Open rkstar opened 9 years ago

rkstar commented 9 years ago

i've got a brand new digital ocean droplet that i'm trying to deploy to which is throwing this error. mupx setup works fine, then mupx deploy chokes and throw this error:

x Invoking deployment process: FAILED

    -----------------------------------STDERR-----------------------------------
    Error response from daemon: no such id: myapp-frontend
    Error: failed to remove containers: [myapp-frontend]
    Error response from daemon: Cannot start container 8ee2840a7e64c60176838afe52e5fb94449e78e213de55550ccf505e2d2697d4: [8] System error: invalid argument
    -----------------------------------STDOUT-----------------------------------
    myapp
    base: Pulling from meteorhacks/meteord
    ef3dfc2694a4: Already exists
    a73c7fdae2e3: Already exists
    f55c06e43d45: Already exists
    e1ded6bbd435: Already exists
    4ccb6ad7cc45: Already exists
    4f80394a6bf4: Already exists
    644b344b6e8b: Already exists
    528baf8d4263: Already exists
    Digest: sha256:3c091d2a283b696266c3044f87d2cc8595f9ac837b2de7835cd1af0080aa5f44
    Status: Image is up to date for meteorhacks/meteord:base
    8ee2840a7e64c60176838afe52e5fb94449e78e213de55550ccf505e2d2697d4
    ----------------------------------------------------------------------------

i've been able to deploy another codebase to 4 other DO droplets successfully. only difference with this project is that its only server code. i did add a /client dir with a simple html file but that made no difference.

the app builds fine locally.

MasterJames commented 9 years ago

If you moved the line.. https://github.com/arunoda/meteor-up/blob/mupx/templates/linux/start.sh#L17

set +e

to before line 10 in the mupx start.sh https://github.com/arunoda/meteor-up/blob/mupx/templates/linux/start.sh#L10

that might make it go?!

mkpazon commented 8 years ago

Encountered this problem myself. I am using Vultr+Ubuntu. Realized that Apache server is running by default so I had to disable Apache to let Nginx do its job. I followed the disabling of Apache server here. After disabling Apache everything seems to be working.