3 months ago
logs:
1
FROM mcr.microsoft.com/playwright/python:latest@sha256:98e
13ms
internal
load build context
WORKDIR /app
2s
3
COPY requirements.txt /app/requirements.txt
113ms
4
RUN pip install --no-cache-dir -r /app/requirements.txt
2s
[notice] To update, run: python -m pip install --upgrade pip
5
COPY . /app
150ms
6
RUN playwright install --with-deps || true
28s
Webkit 17.4 (playwright build v1944) downloaded to /ms-playwright/webkit-1944
exporting to docker image format
15s
containerimage.descriptor: eyJtZ
containerimage.config.digest: sha256:a9f4
containerimage.digest: sha256:35
image push
1.2 GB / 1.2 GB23.4s
=========================
Container failed to start
=========================
Failed to start deployment.
If this error persists, please reach out to the Railway team at https://station.railway.com.
18 Replies
3 months ago
Hey, do you see any kind of logs on the deploy logs tab?
hi thanks for your input but now i have fixed the issue debugging myself this can be closed now
3 months ago
Great, if you can share what happened it would really help for future users 🙂
yes it was my first time using playwright python on railway so , ill make a full tutorial if there is an option here
i have a cron job to run hourly , to test it i cliked the run now button now even though run is complete the output is delivered it still says running here

3 months ago
For Playwright we always recommend using https://railway.com/deploy/0jqemX
3 months ago
Can you share a screenshot of your runs? (Just click on the service)
3 months ago
Thanks, can you share your service link? (the one on your browser)
3 months ago
!t
3 months ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response passos • 3 months ago
3 months ago
I'll wait on the team here but might just be a visual bug
Scheduled services should exit as soon as they are done with the task they are responsible to perform. Thus, the process should close any connections, such as database connections, to exit properly.
Currently, Railway does not automatically terminate deployments. As a result, if a previous execution is still running when the next scheduled execution is due, Railway will skip the new cron job. i found this could it be the reason?
3 months ago
Your cronjob is not running, it would be shown in the interface like this.

Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 3 months ago
