Segmentation fault no matter what i have in my Dockerfile

I just hit my head on this while experimenting with ubuntu:21.10 and falling back to ubuntu:latest got it working.

1 Like

@kurt I have the same issue with hexpm/elixir:1.13.3-erlang-24.3.1-ubuntu-impish-20211102. I can’t seem to build anything based on impish with fly.

My latest theory is a change in our guest kernels made them incompatible with some of our host kernels. This is a long shot, but I can start testing older kernels.

In the meantime, we will accelerate our plan for rolling out host kernel upgrades.


We are still working on this, we do not have a quick fix. It’s frustrating and a shit user experience, we’ll get it fixed.


By the way, this seems to affect Ubuntu 21.01 images. And presumably something recent in archlinux:base-devel. If you switch to Ubuntu 20.01 you might get unstuck.

@ryansch I just realized you said that but I didn’t recognize impish at the time. :slight_smile:

1 Like

I also ran into this issue with impish, but seemingly only when also using a volume.

Anything I can do about it? I really can’t work like this

1 Like

The latest node:alpine docker image doesn’t work. (Works fine locally)

v265 failed - Failed due to unhealthy allocations - not rolling back to stable job version 265 as current job has same specification and deploying as v266

Upgrading the kernel on all our hosts means a downtime period and careful planning :slight_smile:

This is something we’ve been meaning to do, but there’s a lot going on at Fly and we’re not a big team yet.

You should pin your FROM to a more specific tag. You probably don’t need / want to always be on node:alpine or else you might deploy one day and be on a completely different node.js and / or alpine version. This could break your app in odd ways.

We do want people to be able to run any image on us, so we’re definitely going to fix it.


Will that hit the blog when you do?

That should hit the changelog when it happens!


ubuntu:latest doesn’t work as well

Any update about this yet? Don’t want to seem pushy, just checking in if there’s new info!

We had to delay our host kernel upgrade maintenance the other day because we found another issue.

We’ve implemented a fix for this other issue and are still observing.

We should be able to reschedule the host kernel upgrade maintenance soon and it should fix this segmentation fault issue.


Can I hijack this thread to ask you how to spin up a plain ol’ ubuntu instance on fly (that I can ssh into?)

Right now I’m getting Failed due to unhealthy allocations on deploy, presumably because my container exits and doesn’t wait for any incoming SSH connections.

2022-07-08T19:03:52Z   [info]2022/07/08 19:03:52 listening on [fdaa:0:6cb4:a7b:23c6:6cf7:258a:2]:22 (DNS: [fdaa::3]:53)
2022-07-08T19:03:53Z   [info]Main child exited normally with code: 0
2022-07-08T19:03:53Z   [info]Starting clean up.
--> v3 failed - Failed due to unhealthy allocations - no stable job version to auto revert to and deploying as v4

Is there a recommended way of doing this on fly?

For the record, I want to spin up an Ubuntu instance to test connecting to my redis app on using an .internal address!

Try putting CMD ["sleep", "infinity"] at the end of your Dockerfile. And put an empty [[services]] block in fly.toml.


This worked. Thank you!

@technillogue @ryansch @codearchitect @merlin we’ve upgraded our hosts today and using these images should now work everywhere.


I just shipped a phx app with:

ARG BUILDER_IMAGE="hexpm/elixir:1.13.4-erlang-25.0.2-ubuntu-jammy-20220428"
ARG RUNNER_IMAGE="ubuntu:jammy-20220428"