this does not belong in docs; nobody should be manually editing the PATH, only sourcing nvm.sh and letting nvm do it.

it's also not necessary here since nvm install handles it in the next RUN statement.

doesn't each run in docker happen in a new shell? iirc, mutating your env in a RUN doesn't persist in downstream runs

Yes - but instead of hardcoding the PATH, is there a way the RUN that sources nvm.sh could export the resulting PATH for further RUNs to use?

@ljharb @cdargine ENV PATH="$NVM_DIR/versions/node/v$NODE_VERSION/bin:$PATH" sholdnt this export the path to resulting run commands ?

he's looking for something like ENV=$(/path/to/nvm env) I think. Feel free to push to or close this or, btw.

@ljharb, i have been thinking about it, and I don't see a way forward otherwise, which is disappointing. ENV stanzas do not accept child commands, so we are left with only build args, the file system, and RUN blocks as sources of dynamic input, however only build arg inputs can be pulled into the image ENV definition from what i can tell. or, better said, i cannot find a way to dynamically promote content from within a build step to the image ENV. if ENV PATH=$PATH;$(nvm path) worked, we would have a clean solve. it does not.

In that case, a paragraph in the docs that explains these things clearly (including to me, who has minimal docker experience) might be a good way to resolve this PR?

I think I found a pretty neat way of installing nvm in a docker container by leveraging the bash environment variable $BASH_ENV, this way we don't even need to make the bash in the container into an interactive/login shell.

FROM ubuntu:22.10
SHELL ["/bin/bash", "-o", "pipefail", "-c"]

ENV BASH_ENV /root/.env
RUN touch $BASH_ENV
RUN echo '. "'"$BASH_ENV"'"' >> ~/.bashrc # only needed if executing interactively into the container

RUN apt-get update && apt-get install -y curl
RUN curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.2/install.sh | PROFILE="$BASH_ENV" bash

COPY .nvmrc .nvmrc
RUN nvm install
RUN node -v

This way nvm+node is easily available both later in the Dockerfile, and when executing into the container

> echo 19.0.1 > .nvmrc
> docker build -t foo .
...
Step 9/10 : RUN nvm install
Found '//.nvmrc' with version <19.0.1>
...
Now using node v19.0.1 (npm v8.19.2)
Creating default alias: default -> 19.0.1 (-> v19.0.1 *)
...
Step 10/10 : RUN node -v
v19.0.1
> docker run --rm -it --entrypoint bash foo
root@4e5088bdde4d:/# tail -1 ~/.bashrc
. "/root/.env"
root@4e5088bdde4d:/# node -v
v19.0.1

Maybe it's neat enough to fit in the readme?

That does seem pretty compelling.

Do you think that would be a replacement for this PR? If so, please post a link to a branch (NOT a new PR) and i'll pull in the changes. If not, please file a new PR :-)

Yeah I think it could be.

Sure!
https://github.com/blole/nvm/tree/docs/install-in-docker

I tried my hand at updating the Dockerfile in the repo as well, it seems to work like I'd expect, but I'm not sure what people use it for, so I can't really verify that.