c0b

I think your case just need to launch a prebuilt chrome image to run some testing, use volume mounting your code space, and run your override cmd ; don't even...

it could be due to `--enable-benchmarking` or `--enable-net-benchmarking` you may drop both https://github.com/c0b/chrome-in-docker/blob/master/supervisord.conf#L22-L23

this can be done as part of #122 example in https://github.com/c0b/docker-elixir/issues/122#issuecomment-640890167

the building process of this repo's images does not add any Python layer, so these Python versions just exist in the base debian image layers; once official-images use a newer...

> Then under each dir like `22/` have a build for elixir on that OTP version. then what's further directory layout under `22/`? is it a separate repo https://github.com/erlang/docker-erlang-otp/issues/245#issuecomment-545267828 22.0-elixir-alpine...

looks like some breaking changes, and makes this as a completely different repo; because all your repo will look like this, under one flat root directory, there's only one `build-all`...

could you tell which latest images (with sha256) have the problems? I am checking it as of now, get the `elixir:1.8.2-alpine@sha256:36f0e4f55851db29ec9ff7ad5f309266967bd13647a55d508408509d9bbb4d37`, with the default cmd is `iex` when `iex` works,...

the `/config/config.exs` should be from your own project, are you sure it's properly mounted to the container?

it's the XWindow protocol not mismatch, for me I I run Linux as the main developer OS only, on Mac hardware and other PC laptops, I like the Mac hardware...

@hopewise can confirm that? then we may add a section into the wiki page, and a link to the README.md https://github.com/c0b/docker-elixir/wiki/use-observer