Railway Deployment #3648d8 fix: remove unsupported VOLUME#1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The Railway build failed at BUILD_IMAGE with "dockerfile invalid: docker VOLUME at Line 21 is not supported, use Railway Volumes" because the Dockerfile declared VOLUME ["/data"], which Railway's Dockerfile builder rejects.
Solution
Removed the VOLUME ["/data"] instruction from the Dockerfile. The app still creates and writes to /data via RUN mkdir -p /data and BEDFLOW_DATA_DIR=/data; to persist this directory across deploys, attach a Railway Volume mounted at /data via the dashboard.
Changes
DockerfileContext
9c89e81Generated by Railway