vector-im-hydrogen-web/Dockerfile

FROM --platform=${BUILDPLATFORM} docker.io/library/node:16.13-alpine3.15 as builder
RUN apk add --no-cache git python3 build-base
WORKDIR /app

# Install the dependencies first
COPY yarn.lock package.json ./
RUN yarn install

# Copy the rest and build the app
COPY . .
RUN yarn build

FROM --platform=${TARGETPLATFORM} docker.io/nginxinc/nginx-unprivileged:1.21-alpine
COPY --from=builder /app/target /usr/share/nginx/html
Multi-arch capable Dockerfile 2022-02-02 15:26:02 +01:00			`FROM --platform=${BUILDPLATFORM} docker.io/library/node:16.13-alpine3.15 as builder`
Required pkg for aarch64 docker build 2021-09-30 04:31:39 +02:00			`RUN apk add --no-cache git python3 build-base`
chore: optimise Dockerfile So far, the Dockerfile built hydrogen on the server running the image, instead of building it during the building of the image. This blew up the image size immensely and caused node+yarn to run in the resulting image. This new Dockerfile builds hydrogen in a separate build stage and then moves the target directory into an nginx based container image, which takes care of serving the target webroot. The existing Dockerfile has been moved to Dockerfile-dev for usage as a development environment. The docs have been adjusted accordingly. Additionally, this switched from a fixed alpine version of the node image to the latest alpine version, and changed the container image references in the `FROM` statements to use the fully qualified references including the registry domain. 2021-03-08 17:02:04 +01:00			`WORKDIR /app`

Multi-arch capable Dockerfile 2022-02-02 15:26:02 +01:00			`# Install the dependencies first`
			`COPY yarn.lock package.json ./`
			`RUN yarn install`

			`# Copy the rest and build the app`
			`COPY . .`
			`RUN yarn build`

Use non-root nginx base in Docker image 2022-02-02 15:33:10 +01:00			`FROM --platform=${TARGETPLATFORM} docker.io/nginxinc/nginx-unprivileged:1.21-alpine`
chore: optimise Dockerfile So far, the Dockerfile built hydrogen on the server running the image, instead of building it during the building of the image. This blew up the image size immensely and caused node+yarn to run in the resulting image. This new Dockerfile builds hydrogen in a separate build stage and then moves the target directory into an nginx based container image, which takes care of serving the target webroot. The existing Dockerfile has been moved to Dockerfile-dev for usage as a development environment. The docs have been adjusted accordingly. Additionally, this switched from a fixed alpine version of the node image to the latest alpine version, and changed the container image references in the `FROM` statements to use the fully qualified references including the registry domain. 2021-03-08 17:02:04 +01:00			`COPY --from=builder /app/target /usr/share/nginx/html`