audiobookshelf/Dockerfile

### STAGE 0: Build client ###
FROM node:20-alpine AS build
WORKDIR /client
COPY /client /client
RUN npm ci && npm cache clean --force
RUN npm run generate

### STAGE 1: Build server ###
FROM sandreas/tone:v0.1.5 AS tone
FROM node:20-alpine

ENV NODE_ENV=production

RUN apk update && \
    apk add --no-cache --update \
    curl \
    tzdata \
    ffmpeg \
    make \
    python3 \
    g++ \
    tini

COPY --from=tone /usr/local/bin/tone /usr/local/bin/
COPY --from=build /client/dist /client/dist
COPY index.js package* /
COPY server server

RUN npm ci --only=production

RUN apk del make python3 g++

EXPOSE 80

ENTRYPOINT ["tini", "--"]
CMD ["node", "index.js"]
Change: support more architectures in Dockerfile 2021-10-23 13:18:58 +02:00			`### STAGE 0: Build client ###`
Update to node20 - updates many dependencies - removes @nuxtjs/tailwindcss and postcss8 - pkg targets are using node18 until node20 targets are available 2024-01-20 00:54:41 +01:00			`FROM node:20-alpine AS build`
Init 2021-08-18 00:01:11 +02:00			`WORKDIR /client`
			`COPY /client /client`
Update dockerfile for generating client 2022-05-25 17:26:21 +02:00			`RUN npm ci && npm cache clean --force`
Init 2021-08-18 00:01:11 +02:00			`RUN npm run generate`

Change: support more architectures in Dockerfile 2021-10-23 13:18:58 +02:00			`### STAGE 1: Build server ###`
Update:Bump tone version Addresses #1703. Paths with quotations were not handled by tone<v0.1.3. 2023-04-19 23:22:08 +02:00			`FROM sandreas/tone:v0.1.5 AS tone`
Update to node20 - updates many dependencies - removes @nuxtjs/tailwindcss and postcss8 - pkg targets are using node18 until node20 targets are available 2024-01-20 00:54:41 +01:00			`FROM node:20-alpine`
Add:Experimental tone library for scanning metadata 2022-09-11 22:35:06 +02:00
Init 2021-08-18 00:01:11 +02:00			`ENV NODE_ENV=production`
Increase heap size to 4gb in Dockerfile 2023-07-17 14:48:23 +02:00
feat: Updates to docker file and gh action * Clean up Dockerfile * Add health check to Dockerfile * Update gh action versions 2022-06-02 07:55:01 +02:00			`RUN apk update && \`
			`apk add --no-cache --update \`
			`curl \`
			`tzdata \`
Update Dockerfile for sqlite3, update models for cascade delete, fix backup schedule 2023-07-09 18:39:15 +02:00			`ffmpeg \`
			`make \`
			`python3 \`
Add tini as PID 1 handler in container image This PR adds `tini` to the container image and uses it as PID 1 when starting the container. This ensures that proper PID 1 signal-handling is implemented and passed to the underlying node.js process, thereby ensuring that the ABS process has a chance to receive and handle signals other than `SIGKILL`, such as the important `SIGINT`. This is somewhat related to #2445 . Without this, the signal handled by 2445 won't be received when running in a container. Some background: In linux, PID 1 has special duties involving signal handling that are different than other processes. Node doesn't properly handle these signals, which can lead to a number of problems ranging from annoying to disruptive. PID 1 also has reaping duties that can lead to resource exhaustion if not properly handled. For example, the container ignores `SIGINT` (Ctrl+C) as well as `docker stop`, which can be annoying in development as you have to kill or wait for the timeout to be reached. In a production environment (such as Kubernetes) this can lead to signal escalation and unnecessarily adds delays to deployments and restarts as K8s has to wait for the timeout to be reached before sending `SIGKILL`. At best this is annoying and unnecessarily adds delays. At worst this can lead to file/data corruption as the process doesn't get a chance to clean anything up when it is sent `SIGKILL`. Without a proper PID 1 to forward signals, only SIGKILL can be used to terminate the running process. 2024-01-03 21:55:43 +01:00			`g++ \`
			`tini`
feat: Updates to docker file and gh action * Clean up Dockerfile * Add health check to Dockerfile * Update gh action versions 2022-06-02 07:55:01 +02:00
Add:Experimental tone library for scanning metadata 2022-09-11 22:35:06 +02:00			`COPY --from=tone /usr/local/bin/tone /usr/local/bin/`
Init 2021-08-18 00:01:11 +02:00			`COPY --from=build /client/dist /client/dist`
feat: Updates to docker file and gh action * Clean up Dockerfile * Add health check to Dockerfile * Update gh action versions 2022-06-02 07:55:01 +02:00			`COPY index.js package* /`
Init 2021-08-18 00:01:11 +02:00			`COPY server server`
feat: Updates to docker file and gh action * Clean up Dockerfile * Add health check to Dockerfile * Update gh action versions 2022-06-02 07:55:01 +02:00
Update dockerfile failing with dev dependency 2022-05-21 01:15:54 +02:00			`RUN npm ci --only=production`
feat: Updates to docker file and gh action * Clean up Dockerfile * Add health check to Dockerfile * Update gh action versions 2022-06-02 07:55:01 +02:00
Update Dockerfile for sqlite3, update models for cascade delete, fix backup schedule 2023-07-09 18:39:15 +02:00			`RUN apk del make python3 g++`

Init 2021-08-18 00:01:11 +02:00			`EXPOSE 80`
Update:Remove healthcheck from Dockerfile 2023-07-20 23:59:46 +02:00
Add tini as PID 1 handler in container image This PR adds `tini` to the container image and uses it as PID 1 when starting the container. This ensures that proper PID 1 signal-handling is implemented and passed to the underlying node.js process, thereby ensuring that the ABS process has a chance to receive and handle signals other than `SIGKILL`, such as the important `SIGINT`. This is somewhat related to #2445 . Without this, the signal handled by 2445 won't be received when running in a container. Some background: In linux, PID 1 has special duties involving signal handling that are different than other processes. Node doesn't properly handle these signals, which can lead to a number of problems ranging from annoying to disruptive. PID 1 also has reaping duties that can lead to resource exhaustion if not properly handled. For example, the container ignores `SIGINT` (Ctrl+C) as well as `docker stop`, which can be annoying in development as you have to kill or wait for the timeout to be reached. In a production environment (such as Kubernetes) this can lead to signal escalation and unnecessarily adds delays to deployments and restarts as K8s has to wait for the timeout to be reached before sending `SIGKILL`. At best this is annoying and unnecessarily adds delays. At worst this can lead to file/data corruption as the process doesn't get a chance to clean anything up when it is sent `SIGKILL`. Without a proper PID 1 to forward signals, only SIGKILL can be used to terminate the running process. 2024-01-03 21:55:43 +01:00			`ENTRYPOINT ["tini", "--"]`
Update Dockerfile run command to use node index.js 2023-03-09 18:47:48 +01:00			`CMD ["node", "index.js"]`