9 months ago
You reached the start of the range
Feb 5, 2026, 12:47 PM
=========================
Container failed to start
=========================
Failed to create deployment.
2 Replies
9 months ago
Not terribly informative.
fjblau
Not terribly informative.
20 days ago
What you are seeing is the edge giving up on the container, not the app complaining. "Container failed to start" plus "Failed to create deployment" means the process inside the image exited before Railway could attach a healthy deployment. With the official arangodb image there are three usual causes, in order of likelihood.
-
No auth variable. The image refuses to boot unless one of these is set: ARANGO_ROOT_PASSWORD=, ARANGO_RANDOM_ROOT_PASSWORD=1, or ARANGO_NO_AUTH=1 (see "Choosing an authentication method" in the image docs). Without one, arangod aborts inside the entrypoint before it can write anything to the log, which is why the deploy log looks empty.
-
Port mismatch. Railway injects PORT, but arangod ignores it and listens on 8529. The public networking target port has to be 8529, not whatever Railway guessed. A wrong target port gives you a container that runs and answers nothing.
-
Volume path. Data belongs at /var/lib/arangodb3 (Foxx apps at /var/lib/arangodb3-apps). A volume mounted at /data or /var/lib/arangodb is not used by the image, so the server initialises an empty data directory and redoes it on every deploy.
The combination that works: volume mounted at /var/lib/arangodb3, ARANGO_ROOT_PASSWORD set in the service variables, target port 8529, and the default start command left alone so the entrypoint runs arangod.
You can confirm locally in about 30 seconds. "docker run --rm -p 8529:8529 arangodb:3.12" should fail the same way, and "docker run --rm -p 8529:8529 -e ARANGO_RANDOM_ROOT_PASSWORD=1 arangodb:3.12" should start and print a root password. If the second one runs on your machine but Railway still fails, then it is env, volume or target port rather than the image.
The empty log is the clue, not a gap: an entrypoint that aborts never gets far enough to stream anything. So set ARANGO_ROOT_PASSWORD and redeploy first. If the container comes up, that was it. If it starts but the public URL still answers nothing, the target port is the next thing to correct.