https://github.com/kth/kth-nodejs-16
Node 16
https://github.com/kth/kth-nodejs-16
alpine docker nodejs
Last synced: 8 months ago
JSON representation
Node 16
- Host: GitHub
- URL: https://github.com/kth/kth-nodejs-16
- Owner: KTH
- License: mit
- Created: 2021-06-18T21:45:02.000Z (almost 5 years ago)
- Default Branch: main
- Last Pushed: 2025-02-24T15:03:59.000Z (over 1 year ago)
- Last Synced: 2025-03-22T06:01:55.736Z (about 1 year ago)
- Topics: alpine, docker, nodejs
- Language: Shell
- Homepage:
- Size: 42 KB
- Stars: 0
- Watchers: 8
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# NodeJS 16 
## What versions are installed?
*Npm* and *Yarn* versions are always the latest availible at build time.
Each built image has information about its version in a file called `KTH_NODEJS`. To look into this files content run:
```bash
az login
az acr login -n kthregistry
docker run kthregistry.azurecr.io/kth-nodejs-16 cat /KTH_NODEJS
```
```bash
IMAGE INFORMATION
Based on: node:16-alpine
Build date: Sun Jun 20 23:18:18 UTC 2021
Node: v16.3.0
NPM: 7.15.1
Yarn: 1.22.5
--- Default global packages ---
/usr/local/lib
+-- merge-descriptors@1.0.1
`-- npm@7.15.1
```
## Tags
By default there will always be 2 tags to every build.
The first tag contains date of the build, buildversion and 4 first chars from that builds commit sha.
the second is "latest" there will always only one latest version, replacing the previous version.
This will provide a linear insight in the build history.
## What operating system does this image use?
The image also contains build information from when the operating system was built. This information is located in the root in a file called `KTH_OS` run: `docker run kthregistry.azurecr.io/kth-nodejs-16 cat /KTH_NODEJS`. to view your image, and make sure you are logged in to the ACR as mentioned above.
```bash
Alpine version: 3.13.5
Build date: Sun Jun 20 23:18:18 UTC 2021
```
## Automated builds
There is a schedule for nightly build. New builds are scheduled for 5 times a week. Builds are also automated to trigger when the code in main branch is updated.