Docker is only a set of restrictions in terms of system calls, process visibility, filesystem access and networking. There is no hypervisor or virtual CPU.
binarytemple
wdiechmann
restlessronin
I’m also on a Mac M1, and running in container to bypass the non-availability of M1 builds of a lot of OSS.
I seem to be running into a similar issue with Phoenix 1.6.4 with a freshly minted app. I tried using
FROM hexpm/elixir:1.13.0-erlang-24.1.7-ubuntu-focal-20210325
If I run esbuild natively, it works. If I run esbuild in container, it segfaults. esbuild seems to be using esbuild-darwin-arm64 natively, but esbuild-linux-arm64 in container. Not sure if this is the root cause.
When I run mix phx.server, it just seems to hang. I never get the “[info] Running Crypto.Endpoint with cowboy 2.9.0 at 0.0.0.0:4000 (http)” output.
I have a feeling this is being caused by esbuild (maybe the watchers), but don’t know how to confirm that.
I’m an erlang/elixir noob, but otherwise pretty experienced. I’m not sure how to go about finding the point at which such a crash might be happening (if it is). Any pointers to the process of diagnosis would be just as helpful as an actual answer. I’m happy to get my hands dirty with low level detail on elixir/erlang/otp.
0
restlessronin
I tried the following native
Elixir: 1.12.3
Erlang: 24.1
phx_new: 1.6.4
I created a new phoenix project with no db and no mailer.
mix phx.new . --app crypto --no-ecto --no-mailer
mix phx.server
I get the same hanging behaviour that I do in container. The difference is that
mix assets.deploy
works natively, but segfaults in container
So maybe this is an issue with the M1 rather than containerization
How would I go about finding out why/where it’s hanging. Is there a way to log events on the request path? or attach a debugger? some other tool that I’m unaware of?
0
restlessronin
Looks like part of the problem was with the app name. I guess “crypto” is an existing name somewhere. I changed the app name and it’s running natively now.
In container, I still get a segfault, but now I get the output
“[info] Running MyAppWeb.Endpoint with cowboy 2.9.0 at 127.0.0.1:4000 (http)” output.
so at least it’s getting further. My guess is it’s still something to do with esbuild, darwin vs linux.
Any pointers on how to diagnose would be useful.
0
restlessronin
I got it running in container by commenting out the esbuild watcher
watchers: [
# Start the esbuild watcher by calling Esbuild.install_and_run(:default, args)
# esbuild: {Esbuild, :install_and_run, [:default, ~w(--sourcemap=inline --watch)]}
]
0
restlessronin
restlessronin
It turns out phx.new was generating an older version of esbuild (0.13.5). The new version 0.14.0 appears to be working correctly in container. It’s also the default version used in the current version of the phoenix esbuild installer.
PR submitted.
https://github.com/phoenixframework/phoenix/pull/4630
2
restlessronin
binarytemple
Portmanteau of binary (because computers, and another pun) and temple - part of the name of a particularly crappy company I worked at when I was young and desperate for work.
1