[bitnami/node] Release 18.19.0-debian-11-r4 (#55092)

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
This commit is contained in:
Bitnami Bot
2024-01-20 02:35:32 +01:00
committed by GitHub
parent 8e1b9954ce
commit 0ba204adf8
4 changed files with 9 additions and 74 deletions
+3 -2
View File
@@ -7,10 +7,10 @@ ARG TARGETARCH
LABEL com.vmware.cp.artifact.flavor="sha256:1e1b4657a77f0d47e9220f0c37b9bf7802581b93214fff7d1bd2364c8bf22e8e" \
org.opencontainers.image.base.name="docker.io/bitnami/minideb:bullseye" \
org.opencontainers.image.created="2024-01-03T08:08:18Z" \
org.opencontainers.image.created="2024-01-20T00:42:12Z" \
org.opencontainers.image.description="Application packaged by VMware, Inc" \
org.opencontainers.image.licenses="Apache-2.0" \
org.opencontainers.image.ref.name="18.19.0-debian-11-r3" \
org.opencontainers.image.ref.name="18.19.0-debian-11-r4" \
org.opencontainers.image.title="node" \
org.opencontainers.image.vendor="VMware, Inc." \
org.opencontainers.image.version="18.19.0"
@@ -39,6 +39,7 @@ RUN mkdir -p /tmp/bitnami/pkg/cache/ ; cd /tmp/bitnami/pkg/cache/ ; \
done
RUN apt-get update && apt-get upgrade -y && \
apt-get clean && rm -rf /var/lib/apt/lists /var/cache/apt/archives
RUN find / -perm /6000 -type f -exec chmod a-s {} \; || true
RUN mkdir /.npm && chmod g+rwX /.npm
RUN sed -i 's/^PASS_MAX_DAYS.*/PASS_MAX_DAYS 90/' /etc/login.defs && \
sed -i 's/^PASS_MIN_DAYS.*/PASS_MIN_DAYS 0/' /etc/login.defs && \
@@ -1,14 +0,0 @@
# Copyright VMware, Inc.
# SPDX-License-Identifier: APACHE-2.0
version: '2'
services:
node:
tty: true # Enables debugging capabilities when attached to this container.
image: docker.io/bitnami/node:18
# command: sh -c 'npm install && npm start'
ports:
- 3000:3000
volumes:
- .:/app
@@ -10,7 +10,7 @@ fi
script=$1
exit_code="${2:-96}"
fail_if_not_present="${3:-y}"
fail_if_not_present="${3:-n}"
if test -f "$script"; then
sh $script
+5 -57
View File
@@ -10,14 +10,7 @@ Trademarks: This software listing is packaged by Bitnami. The respective tradema
## TL;DR
```console
docker run -it --name node bitnami/node
```
### Docker Compose
```console
curl -sSL https://raw.githubusercontent.com/bitnami/containers/main/bitnami/node/docker-compose.yml > docker-compose.yml
docker-compose up -d
docker run -it --name node bitnami/node:latest
```
## Why use Bitnami Images?
@@ -211,16 +204,6 @@ We may want to make our Node.js web server only accessible via an nginx web serv
docker network create app-tier --driver bridge
```
or using Docker Compose:
```yaml
version: '2'
networks:
app-tier:
driver: bridge
```
#### Step 2: Create a virtual host
Let's create an nginx virtual host to reverse proxy to our Node.js container.
@@ -254,19 +237,6 @@ docker run -it --name myapp --network app-tier \
bitnami/node node index.js
```
or using Docker Compose:
```yaml
version: '2'
myapp:
image: bitnami/node
command: node index.js
networks:
- app-tier
volumes:
- .:/app
```
#### Step 4: Run the nginx image
```console
@@ -276,18 +246,6 @@ docker run -it \
bitnami/nginx
```
or using Docker Compose:
```yaml
version: '2'
nginx:
image: bitnami/nginx
networks:
- app-tier
volumes:
- /path/to/vhost.conf:/bitnami/nginx/conf/vhosts/yourapp.conf:ro
```
## Maintenance
### Upgrade this image
@@ -300,20 +258,12 @@ Bitnami provides up-to-date versions of Node.js, including security patches, soo
docker pull bitnami/node:latest
```
or if you're using Docker Compose, update the value of the image property to `bitnami/node:latest`.
#### Step 2: Remove the currently running container
```console
docker rm -v node
```
or using Docker Compose:
```console
docker-compose rm -v node
```
#### Step 3: Run the new image
Re-create your container from the new image.
@@ -322,14 +272,12 @@ Re-create your container from the new image.
docker run --name node bitnami/node:latest
```
or using Docker Compose:
```console
docker-compose up node
```
## Notable Changes
### Starting January 16, 2024
* The `docker-compose.yaml` file has been removed, as it was solely intended for internal testing purposes.
### 6.2.0-r0 (2016-05-11)
* Commands are now executed as the `root` user. Use the `--user` argument to switch to another user or change to the required user using `sudo` to launch applications. Alternatively, as of Docker 1.10 User Namespaces are supported by the docker daemon. Refer to the [daemon user namespace options](https://docs.docker.com/engine/security/userns-remap/) for more details.