docker - CoreOS Unit Failed on Launched -


i tried launching service using chat.service unit file on coreos , failed:

// chat.service [unit] description=chatapp  [service] execstartpre=-/usr/bin/docker kill simplechat1 execstartpre=-/usr/bin/docker rm simplechat1 execstartpre=-/usr/bin/docker pull jochasinga/socketio-chat execstart=/usr/bin/docker run -p 3000:3000 --name simplechat1 jochasinga/socketio-chat 

fleetctl list-units shows:

unit            machine                     active  sub chat.service    cfe13a03.../<virtual-ip>    failed  failed 

however, if changed chat.service just:

// chat.service [service] execstart=/usr/bin/docker run -p 3000:3000 <mydockerhubuser>/socketio-chat 

it ran fine. fleetctl list-units shows:

unit            machine                     active  sub chat.service    8df7b42d.../<virtual-ip>    active  running 

edit using journalctl -u chat.service got:

jun 02 00:02:47 core-01 systemd[1]: started chat.service. jun 02 00:02:47 core-01 systemd[1]: chat.service: main process exited, code=exited, status=125/n/a jun 02 00:02:47 core-01 docker[8924]: docker: error response daemon: failed create endpoint clever_tesla on network brid jun 02 00:02:47 core-01 systemd[1]: chat.service: unit entered failed state. jun 02 00:02:47 core-01 systemd[1]: chat.service: failed result 'exit-code'. jun 02 00:02:58 core-01 systemd[1]: stopped chat.service. jun 02 00:03:08 core-01 systemd[1]: stopped chat.service. 

what had done wrong in first chat.service unit file? guidance appreciated.

running vagrant version of coreos (stable) on mac os x.

your execstartpre= command doesn't seem have docker subcommand in it. did mean use pull?

reading journal unit should more information: journactl -u chat.service


Popular posts from this blog

php - How should I create my API for mobile applications (Needs Authentication) -

5 Reasons to Blog Anonymously (and 5 Reasons Not To)

Google AdWords and AdSense - A Dynamic Small Business Marketing Duo