Skip to content

NOTES.md

Latest commit

 

History

History
39 lines (24 loc) · 1.48 KB

NOTES.md

File metadata and controls

39 lines (24 loc) · 1.48 KB

Using nvm from postCreateCommand or another lifecycle command

Certain operations like postCreateCommand run non-interactive, non-login shells. Unfortunately, nvm is really particular that it needs to be "sourced" before it is used, which can only happen automatically with interactive and/or login shells. Fortunately, this is easy to work around:

Just can source the nvm startup script before using it:

"postCreateCommand": ". ${NVM_DIR}/nvm.sh && nvm install --lts"

Note that typically the default shell in these cases is sh not bash, so use . ${NVM_DIR}/nvm.sh instead of source ${NVM_DIR}/nvm.sh.

Alternatively, you can start up an interactive shell which will in turn source nvm:

"postCreateCommand": "bash -i -c 'nvm install --lts'"

OS Support

Debian/Ubuntu, RedHat Enterprise Linux, Fedora, Alma, and Rocky Linux distributions with the apt, yum, dnf, or microdnf package manager installed.

Note: RedHat 7 Family (RedHat, CentOS, etc.) must use Node versions less than 18 due to its system libraries and long-term support (LTS) policies.

bash is required to execute the install.sh script.

Setting a private Node.js mirror

If you need to use a private mirror for downloading Node.js binaries (e.g. in an air-gapped environment), you can use the nvmNodeJsOrgMirror option:

"features": {
    "ghcr.io/devcontainers/features/node:1": {
        "nvmNodeJsOrgMirror": "https://my-private-registry.com/node-dist"
    }
}