a month ago
I have been trying to deploy a build for a while now on two different environments.
One environment the build process kept going for 40+ minutes with once exceeding 50 minutes. It kept being stuck on this command:
RUN sudo apt-get update && sudo apt-get install -y --no-install-recommends libnss3 libatk1.0-0 libatk-bridge2.0-0 libcups2 libgbm1 libasound2t64 libpangocairo-1.0-0 libxss1 libgtk-3-0 libxshmfence1 libglu1 chromium
I thought it was an environment issue so I tried testing a simple push on another environment and still the same issue is occurring.
I tried redeploying already deployed and built instances however I ran into the same time problem.
Edit: Still not working, seems very inconsistent with nixpacks. It sometimes decides to install everything from the start and sometimes it is good.
3 Replies
a month ago
We can see two of your services are currently stuck in BUILDING status. Since build cache is not guaranteed on our platform (as the build system scales up and down based on demand), builds that install heavy packages like Chromium and its dependencies via apt-get will be slow whenever the cache is missed. For redeployments specifically, note that a redeploy always triggers a full rebuild. To get more consistent build times, we recommend building a custom Docker image with those system dependencies pre-installed and deploying from that image directly, which avoids the apt-get install step entirely during builds.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
We can see two of your services are currently stuck in BUILDING status. Since build cache is not guaranteed on our platform (as the build system scales up and down based on demand), builds that install heavy packages like Chromium and its dependencies via `apt-get` will be slow whenever the cache is missed. For redeployments specifically, note that a redeploy always triggers a full rebuild. To get more consistent build times, we recommend building a custom Docker image with those system dependencies pre-installed and deploying from that image directly, which avoids the `apt-get install` step entirely during builds.
a month ago
I never faced the issue with any deployment like that till now and those heavy packages have been there in the project for a while now so i doubt that that is the problem.
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Open Railway • about 1 month ago
Status changed to Solved ramboprog • about 1 month ago
a month ago
It turned out that it needed to download all packages again for the first time and then it is back to 3 minute deployments again.
edit (not solved)
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Solved ramboprog • about 1 month ago