William Perron

For reference I pinned the version of Alpine to 3.13 [a few months ago](https://github.com/denoland/deno_docker/pull/153) because version 3.14 had a known issue with Make that crashed the build.

Probably easier to instead change the `DENO_DIR` to be `$HOME/.deno` instead of the current `/deno-dir`

> It's supposed to be accessible by both `root` and `deno`, so I don't think the standard home folder should apply here. > > For the same reason, [the devcontainers...

> ``` > ❯ docker run --rm --user deno denoland/deno:latest install https://deno.land/std/examples/welcome.ts > Download https://deno.land/std/examples/welcome.ts > Warning Implicitly using latest version (0.106.0) for https://deno.land/std/examples/welcome.ts > Download https://deno.land/[email protected]/examples/welcome.ts > Check https://deno.land/std/examples/welcome.ts...

> @wperron do you agree that `deno install` must work out-of-the-box for both `root` and `deno` user? Sorta: I think the use cases for `deno install` in a Docker container...

I don't mind deprecating `centos` in favor of something else, though it's worth noting that Rocky linux is also a popular replacement for Centos now, also `amazonlinux2` is based off...

`oraclelinux` is off the table :upside_down_face:

I don't mind this being a breaking change for the few users that will have behaviors that depend on being run as root, they can update their Dockerfiles to include...

@hayd oh you mean when people are building off of that `deno` image and running additional steps in their Dockerfile, like `apt install` where they might expect to run as...

also `?` and `#` since they have special meaning and effectively "end" the URL