Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I got an error when deploy on Railway #250

Open
issaTan opened this issue Jun 30, 2023 · 5 comments
Open

I got an error when deploy on Railway #250

issaTan opened this issue Jun 30, 2023 · 5 comments

Comments

@issaTan
Copy link

issaTan commented Jun 30, 2023

Thank you for your great job!

When I deploy cusdis on Railway, I got this error: The **VOLUME** keyword is banned in Dockerfiles. Use Railway volumes instead. https://docs.railway.app/reference/volumes.

And I'm a Starter Plan member on Railway, it's because of my account or the settings with cusdis?

@Vinfall
Copy link

Vinfall commented Aug 16, 2023

From my prior experience with Dev plan, just comment out this line and everything should be fine:

VOLUME [ "/data" ]

@greatzh
Copy link

greatzh commented Nov 18, 2023

I encountered this issue also, and I have commented on this line but deployment still failed, is there any other solutions for this problem?

@Vinfall
Copy link

Vinfall commented Nov 19, 2023

I switched to Vercel + self-hosted database now as Railway sunsets dev plan. BTW Vercel has serverless database support too so you can use that instead since Railway requires a $5 minimum cost per month.

The comment above is based on deployment warning on Railway, IIRC it says something like mounting /data is not allowed so I comment the line and it works. Maybe posting the error message here would help.

@greatzh
Copy link

greatzh commented Nov 19, 2023

Thank you for your assistance. The error messages encountered during the deployment process are as follows:
The VOLUME keyword is banned in Dockerfiles. Use Railway volumes instead. https://docs.railway.app/reference/volumes

@Vinfall
Copy link

Vinfall commented Nov 19, 2023

Oh, that's the same error I had on Railway. If commenting this line does not help, I don't know either🤷🏼

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants