Container will only work once about ghost HOT 6 CLOSED

@BjornB2 the default command for the container already starts Ghost, so if you exec into the container and try to start it via ghost start you'll get issues.

from ghost.

I understand, but after booting the container, ghost is not running. Probably due to the same issue.

from ghost.

root@ghost2:/var/lib/ghost# ghost status                                                                                  
┌──────┬──────────┬─────────┬────────┬─────┬──────┬─────────────────┐                                                     
│ Name │ Location │ Version │ Status │ URL │ Port │ Process Manager │                                                     
└──────┴──────────┴─────────┴────────┴─────┴──────┴─────────────────┘                                                     
root@ghost2:/var/lib/ghost#         

from ghost.

So the start command for the container actually doesn't use ghost-cli's start command - it uses the direct node current/index.js command - which is why running ghost status doesn't actually show anything when you run it in the container.

I'm not sure why it wouldn't start fine though - do you have any docker logs from when the container was actually started?

from ghost.

Ok, as usual there seems to be an error between keyboard and chair.
It seems I set my docker port to auto, and I was assuming it would be the same port after a reboot of the container, but it's not. No wonder my browser didn't show the blog..
Sorry for taking up your time. Thanks :)

from ghost.

No problem - glad it's working 😄

from ghost.