Deploying Remix app started failing after many successful deploys on npm install.

I have deployed the app ~30 times successfully and all of a sudden it has started failing (by just frreezing) at the npm install step.

I looked at the builder logs and this is what keeps showing repeatedly:

2022-12-12T14:26:20.386 app[4d89041a263387] ord [info] time="2022-12-12T14:26:20.386553312Z" level=debug msg="found runc process"

2022-12-12T14:26:20.386 app[4d89041a263387] ord [info] time="2022-12-12T14:26:20.386575493Z" level=info msg="containers active, keepalive"

2022-12-12T14:26:20.386 app[4d89041a263387] ord [info] time="2022-12-12T14:26:20.386580663Z" level=debug msg="liveness loop caused deadline reset"

2022-12-12T14:26:21.387 app[4d89041a263387] ord [info] time="2022-12-12T14:26:21.386646502Z" level=debug msg="checking docker activity"

2022-12-12T14:26:21.387 app[4d89041a263387] ord [info] time="2022-12-12T14:26:21.386927609Z" level=debug msg="Calling GET /v1.41/containers/json?filters=%7B%22status%22%3A%7B%22running%22%3Atrue%7D%7D&limit=0"

Strange :thinking:

To see a bit more info about what’s going wrong you could try LOG_LEVEL=debug flyctl deploy and seeing if that reveals more about why. It should show more detail.

Sometimes remote builders do have random issues e.g with networking. It may be worth deleting that builder. Try flyctl apps destroy the-builder-name-goes-here. On your next deploy, Fly will see you have no remote builder and make you another one. If there was some issue with the old one (e.g its disk was full) that will solve it. That’s not worth doing more than once since if the next builder also fails, there is probably something else going wrong.

Thanks Greg! It was a bad builder.

1 Like