Non-web service ('universe-builder') in immediate crash loop
asafcha
HOBBYOP

2 months ago

Hello, I have a service named universe-builder that is stuck in a crash loop.

  1. It is a non-web, worker-style service.

  2. The service fails to stay online even when the start command is set to a simple sleep 3600.

  3. The service does not have a public domain or an active health check configured.

  4. We have tried deploying with both Nixpacks (with an explicit start command) and a Dockerfile, and the result is the same: the container stops immediately after starting.

The issue does not appear to be with the application code but with the service's runtime environment on the platform. Can you please investigate why the container for this service is not staying active?

$10 Bounty

6 Replies

Railway
BOT

2 months ago

Hey there! We've found the following might help you get unblocked faster:

If you find the answer from one of these, please let us know by solving the thread!

fra
HOBBY

2 months ago

do you have an health check? I think the container is killed if there isn't an health check

fra

do you have an health check? I think the container is killed if there isn't an health check

brody
EMPLOYEE

2 months ago

I appreciate you helping the community tremendously, but this isn't true, please verify these kind of claims before mentioning them.

brody

I appreciate you helping the community tremendously, but this isn't true, please verify these kind of claims before mentioning them.

asafcha
HOBBYOP

2 months ago

Thank you for clarifying. Based on your confirmation, we can rule out a missing health check as the cause.

To summarize, this non-web service (universe-builder) enters an immediate crash loop, and we have now exhausted all debugging options on our end:

  1. The service crashes even when its start command is a simple sleep 3600.

  2. We have tried deploying using both the default Nixpacks builder and a custom Dockerfile; both methods result in the same crash loop.

  3. We have confirmed there is no public networking, exposed port, or health check path configured for this service.

    Appreciate you assistance.

brody
EMPLOYEE

2 months ago

Hello,

Unfortunately I cannot help with application or configuration level issues, I'll leave that to the community, I had just popped in to clarify the incorrect information given.

brody

I appreciate you helping the community tremendously, but this isn't true, please verify these kind of claims before mentioning them.

fra
HOBBY

2 months ago

That's why I've said "I think" but I'll pay more attention in the future, thanks

Loading...