Previously working Docker image service not deploying
There are not deploy logs. The build logs are just this:
=========================
Container failed to start
=========================
activity StartToClose timeout
This same service with the same Docker image (Clickhouse template) was working just fine 2 days ago.
21 Replies
Project ID:
8007dc13-e0fa-4bcc-9c09-05e5d5882ba88007dc13-e0fa-4bcc-9c09-05e5d5882ba8
Also experiencing this
this may have been a temporary issue with the builder, is this still a problem?
okay that answers that question lol
Has the root cause been identified, or is it being worked on?
ive asked the team
If you could update us on this thread as soon as you have any news it would be much appreciated.
Hey @Augustus I see the build that failed, I don't see any evidence of ongoing issues. Can you rebuild to see if it was a temporary issue? If we are facing an issue I can confirm it is not wide spread
@aaron are you experiencing this with the clickhouse template as well?
No, it was our own docker container.
The build logs say it is published, but after that nothing seems to happen.
The deploy logs show nothing:
No deployment logs. All output sent to stdout will be displayed hereNormally, when there is a problem with the container, you at least see some error logs, but it doesn't even seem like its attempted to start. Everything works if we build the Docker file locally.
so you arent seeing the "Container failed to start" message?
so you arent seeing the "Container failed to start" message?No, Its my colleague's account but he is not on discord. Shall I get the project ID from him or something?
please open a new help thread as you arent experiencing the same thing as the original poster, and please do get the project id for that
I tried re-deploying, same issue again.
Why don't I see any logs? They would at least add clarity on what's going on.
this is an issue with railway, nothing you did wrong and nothing really for you to debug
We are experiencing an issue that is affecting a small number of users. The team is working on it.
@Augustus Thank you for pushing this to the help queue, and @Brody thanks for bringing this to me, the issue has not been detected by our automatic error detection.
Can you please redeploy one last time @Augustus. I just want to see the issue happen live
@Augustus JR created an issue you can subscribe to https://railway.instatus.com/clnp2ir5l43412bfn1q83e0bbn for when this is resolved
We've fixed the affected host. Can you please redeploy
I just re-deployed, it works π
Just a quick follow-up. I see that the memory usage on this service has shot up to max out at the 8GB account limit. It used to hover at 1.5GB before this issue. Has something changed in the config? Also, would appreciate any tips on how I can change settings in the Clickhouse template, plus a repo link for the clickhouse template would be awesome. I can't seem to find it in https://github.com/orgs/railwayapp-templates/repositories
try restarting the plugin from its settings.
that would likely be via environment variables or flags in the start command.
there is no repo for clickhouse, it is deployed straight from a docker image.