Build from Dockerfile doesn't start
Hey. Hey,
I've been struggling with this for over 8 hours, so far I can't deploy my Laravel/Svelte/Inertia application anywhere. At first I wanted to use docker-compose.yml and host it on Azure, after failing to set it up I reverted to just Dockerfile and Railway. Unfortunately, when I try to build the application and deploy to Railway, the build just won't start, even though Railway found my dockerfile. Does anyone have any idea why this isn't working?
Dockerfile
Lots of love
Luka
21 Replies
Project ID:
155248f7-afe3-42dd-a929-db4f95caa1b6
155248f7-afe3-42dd-a929-db4f95caa1b6
Perhaps related to this issue?
https://railway.instatus.com/cli0abqc0603706ouoat3h3iqe1
Delay in Build & Deploy logs visibility – Incident details - Railwa...
Delay in Build & Deploy logs visibility – Incident details - Railway Status
I see, guess I'll have to wait to be sure haha.
I do think there is more going on under the hood then just a delay in logs-visibility. There are plenty users reporting that their (once working) deploys are failing since today (including myself) without any changes to their code^^
@sheffik The build logs error should be fixed and at least for me my build error has also somehow magically gone away 😄
I'll check it out! Thanks
sadly nothing yet
nvm something is happening
just took a long time
Wait a few seconds/minutes, there seems to be a delay with displaying them. In my case my deployment (build) was already running for 2mins until logs were showing up
yep 😄
yeah I guess it works now
another problem popped up tho haha
but I guess that's on my side
Looks like you've got it, but I do want to note that docker compose is not supported by Railway atm
As a guy who does mainly React/Nuxt, I would've never guessed that deploying a web app could take this long lmao
it requires persistent storage, which Railway does not support
I am not using docker-compose tho
You were, you said so in your first message
just wanted to clear that up
Yeah, I switched up back to just docker, cause I wanted to deploy on railway
but I honestly can't wrap my head around this
Hmm I'm wondering why you do build the docker image (if using nuxt for example) by yourself? IMHO Railway does a great job when letting them handle this step for you. At least for me (but I'm working at the backend part and almost all my projects are running with strapi)
I am building a Laravel/Svelte app
this is a nightmare tbh haha
I got rid of the previous error
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.203. Set the 'ServerName' directive globally to suppress this message
this is the last thing standing in my path I guess
like saintcore said, why not let nixpacks build your app?