Portainer Not Starting
I created a new portainer instance and after I started it for the first time with default settings, it crashed. Here is what was sent to build logs:
=========================
Container failed to start
=========================
We failed to create a container for this image.
Potential reasons for this happening are:
The start command is invalid.
Start command:
docker run -d -p 8000:8000 -p 9443:9443 --name portainer --restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest
The volume is mounted to a directory that is overriding the container's entrypoint.
Mount path: /portainer_data
Im not great with mounts so I'd really appreciate if someone could help me out with this πSolution:Jump to solution
okay then you can completely disregard that template, it seems that someone didn't quite understand what they where doing.
1. you can't use docker run in the start command
2. you can't access the underlying docker deamon, so it's useless on railway...
19 Replies
Project ID:
25f6cdf8-90e3-4387-9483-3e138eba41cc25f6cdf8-90e3-4387-9483-3e138eba41cc
you're using the template right?
yes i am
and that's the default start command?
Solution
okay then you can completely disregard that template, it seems that someone didn't quite understand what they where doing.
1. you can't use docker run in the start command
2. you can't access the underlying docker deamon, so it's useless on railway
thats what i was thinking lol
im not entierly sure how they got this to work
they didn't
you got any ideas then?
it can't work
alright
btw while you're here
if i have a docker container right
and i want to deploy it onto railway
does it just work out of thebox
depends
like say a nodejs container
is the image publicly available from either dockerhub or ghcr?
yep
would it run if railway built the app itself
yep
idek what im asking anymore i dont understand docker a ton and am more confused than when i started thanks for the help though
lol okay