Skip to content

Alpine building and vips working, but lost some build steps#1130

Closed
HuwSy wants to merge 2 commits intobpatrik:masterfrom
HuwSy:master
Closed

Alpine building and vips working, but lost some build steps#1130
HuwSy wants to merge 2 commits intobpatrik:masterfrom
HuwSy:master

Conversation

@HuwSy
Copy link

@HuwSy HuwSy commented Feb 6, 2026

Possible fix for #1122 @bpatrik but I have mistakenly dropped some parts of the old build that maybe I shouldn't have. But it does at least build and render thumbs here under alpine.

PI_DOCKER=true

EXPOSE 80
ARG TARGETARCH
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why did you remove this part? this is for hardware acceleration

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did wonder what this was for and in trying to get changes I understood it came out and ran without, added back now

@bpatrik
Copy link
Owner

bpatrik commented Feb 6, 2026

Thanks you! I made some comments. I could not really test is just yet if it actually works.

@bpatrik
Copy link
Owner

bpatrik commented Feb 6, 2026

It seems that it prevents build on arm/v7:

#45 [linux/arm/v7 runtime 7/9] RUN npm install --omit=dev && npm cache clean --force
#45 118.6 
#45 118.6 added 296 packages, and audited 297 packages in 2m
#45 118.6 
#45 118.6 54 packages are looking for funding
#45 118.6   run `npm fund` for details
#45 118.8 
#45 118.8 5 vulnerabilities (1 moderate, 4 high)
#45 118.8 
#45 118.8 To address all issues, run:
#45 118.8   npm audit fix --force
#45 118.8 
#45 118.8 Run `npm audit` for details.
#45 118.8 npm notice
#45 118.8 npm notice New major version of npm available! 10.8.2 -> 11.9.0
#45 118.8 npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.9.0
#45 118.8 npm notice To update run: npm install -g npm@11.9.0
#45 118.8 npm notice
#45 130.3 npm warn using --force Recommended protections disabled.
#45 DONE 132.8s

#49 [linux/arm/v7 runtime 8/9] RUN mkdir -p /app/data/config   /app/data/db   /app/data/images   /app/data/tmp
#49 DONE 0.1s

#50 [linux/arm/v7 runtime 9/9] RUN ["node", "--expose-gc", "./src/backend/index", "--run-diagnostics", "--config-path=/app/diagnostics-config.json", "--Server-Log-level=silly"]
#50 15.59 /app/node_modules/sharp/lib/sharp.js:121
#50 15.59   throw new Error(help.join('\n'));
#50 15.59   ^
#50 15.59 
#50 15.59 Error: Could not load the "sharp" module using the linuxmusl-arm runtime
#50 15.59 Possible solutions:
#50 15.59 - Manually install libvips >= 8.16.1
#50 15.59 - Add experimental WebAssembly-based dependencies:
#50 15.59     npm install --cpu=wasm32 sharp
#50 15.59     npm install @img/sharp-wasm32
#50 15.59 - Consult the installation documentation:
#50 15.59     See https://sharp.pixelplumbing.com/install
#50 15.59     at Object.<anonymous> (/app/node_modules/sharp/lib/sharp.js:121:9)
#50 15.59     at Module._compile (node:internal/modules/cjs/loader:1521:14)
#50 15.59     at Module._extensions..js (node:internal/modules/cjs/loader:1623:10)
#50 15.59     at Module.load (node:internal/modules/cjs/loader:1266:32)
#50 15.59     at Module._load (node:internal/modules/cjs/loader:1091:12)
#50 15.59     at Module.require (node:internal/modules/cjs/loader:1289:19)
#50 15.59     at require (node:internal/modules/helpers:182:18)
#50 15.59     at Object.<anonymous> (/app/node_modules/sharp/lib/constructor.js:10:1)
#50 15.59     at Module._compile (node:internal/modules/cjs/loader:1521:14)
#50 15.59     at Module._extensions..js (node:internal/modules/cjs/loader:1623:10)
#50 15.59     at Module.load (node:internal/modules/cjs/loader:1266:32)
#50 15.59     at Module._load (node:internal/modules/cjs/loader:1091:12)
#50 15.59     at Module.require (node:internal/modules/cjs/loader:1289:19)
#50 15.59     at require (node:internal/modules/helpers:182:18)
#50 15.59     at Object.<anonymous> (/app/node_modules/sharp/lib/index.js:6:15)
#50 15.59     at Module._compile (node:internal/modules/cjs/loader:1521:14)
#50 15.59 
#50 15.59 Node.js v20.20.0
#50 ERROR: process "node --expose-gc ./src/backend/index --run-diagnostics --config-path=/app/diagnostics-config.json --Server-Log-level=silly" did not complete successfully: exit code: 1
------
 > [linux/arm/v7 runtime 9/9] RUN ["node", "--expose-gc", "./src/backend/index", "--run-diagnostics", "--config-path=/app/diagnostics-config.json", "--Server-Log-level=silly"]:
15.59     at Module._compile (node:internal/modules/cjs/loader:1521:14)
15.59     at Module._extensions..js (node:internal/modules/cjs/loader:1623:10)
15.59     at Module.load (node:internal/modules/cjs/loader:1266:32)
15.59     at Module._load (node:internal/modules/cjs/loader:1091:12)
15.59     at Module.require (node:internal/modules/cjs/loader:1289:19)
15.59     at require (node:internal/modules/helpers:182:18)
15.59     at Object.<anonymous> (/app/node_modules/sharp/lib/index.js:6:15)
15.59     at Module._compile (node:internal/modules/cjs/loader:1521:14)
15.59 
15.59 Node.js v20.20.0
------
WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
Dockerfile.build:86
--------------------
  84 |     
  85 |     # Diagnostics
  86 | >>> RUN ["node", "--expose-gc", "./src/backend/index", "--run-diagnostics", "--config-path=/app/diagnostics-config.json", "--Server-Log-level=silly"]
  87 |     
  88 |     HEALTHCHECK --interval=40s --timeout=30s --retries=3 --start-period=60s \
--------------------
ERROR: failed to build: failed to solve: process "node --expose-gc ./src/backend/index --run-diagnostics --config-path=/app/diagnostics-config.json --Server-Log-level=silly" did not complete successfully: exit code: 1
Error: buildx failed with: ERROR: failed to build: failed to solve: process "node --expose-gc ./src/backend/index --run-diagnostics --config-path=/app/diagnostics-config.json --Server-Log-level=silly" did not complete successfully: exit code: 1

I'm not sure if that is an issue. I think we can just drop it.

@HuwSy
Copy link
Author

HuwSy commented Feb 6, 2026

It seems that it prevents build on arm/v7:

#45 [linux/arm/v7 runtime 7/9] RUN npm install --omit=dev && npm cache clean --force
#45 118.6 
#45 118.6 added 296 packages, and audited 297 packages in 2m
#45 118.6 
#45 118.6 54 packages are looking for funding
#45 118.6   run `npm fund` for details
#45 118.8 
#45 118.8 5 vulnerabilities (1 moderate, 4 high)
#45 118.8 
#45 118.8 To address all issues, run:
#45 118.8   npm audit fix --force
#45 118.8 
#45 118.8 Run `npm audit` for details.
#45 118.8 npm notice
#45 118.8 npm notice New major version of npm available! 10.8.2 -> 11.9.0
#45 118.8 npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.9.0
#45 118.8 npm notice To update run: npm install -g npm@11.9.0
#45 118.8 npm notice
#45 130.3 npm warn using --force Recommended protections disabled.
#45 DONE 132.8s

#49 [linux/arm/v7 runtime 8/9] RUN mkdir -p /app/data/config   /app/data/db   /app/data/images   /app/data/tmp
#49 DONE 0.1s

#50 [linux/arm/v7 runtime 9/9] RUN ["node", "--expose-gc", "./src/backend/index", "--run-diagnostics", "--config-path=/app/diagnostics-config.json", "--Server-Log-level=silly"]
#50 15.59 /app/node_modules/sharp/lib/sharp.js:121
#50 15.59   throw new Error(help.join('\n'));
#50 15.59   ^
#50 15.59 
#50 15.59 Error: Could not load the "sharp" module using the linuxmusl-arm runtime
#50 15.59 Possible solutions:
#50 15.59 - Manually install libvips >= 8.16.1
#50 15.59 - Add experimental WebAssembly-based dependencies:
#50 15.59     npm install --cpu=wasm32 sharp
#50 15.59     npm install @img/sharp-wasm32
#50 15.59 - Consult the installation documentation:
#50 15.59     See https://sharp.pixelplumbing.com/install
#50 15.59     at Object.<anonymous> (/app/node_modules/sharp/lib/sharp.js:121:9)
#50 15.59     at Module._compile (node:internal/modules/cjs/loader:1521:14)
#50 15.59     at Module._extensions..js (node:internal/modules/cjs/loader:1623:10)
#50 15.59     at Module.load (node:internal/modules/cjs/loader:1266:32)
#50 15.59     at Module._load (node:internal/modules/cjs/loader:1091:12)
#50 15.59     at Module.require (node:internal/modules/cjs/loader:1289:19)
#50 15.59     at require (node:internal/modules/helpers:182:18)
#50 15.59     at Object.<anonymous> (/app/node_modules/sharp/lib/constructor.js:10:1)
#50 15.59     at Module._compile (node:internal/modules/cjs/loader:1521:14)
#50 15.59     at Module._extensions..js (node:internal/modules/cjs/loader:1623:10)
#50 15.59     at Module.load (node:internal/modules/cjs/loader:1266:32)
#50 15.59     at Module._load (node:internal/modules/cjs/loader:1091:12)
#50 15.59     at Module.require (node:internal/modules/cjs/loader:1289:19)
#50 15.59     at require (node:internal/modules/helpers:182:18)
#50 15.59     at Object.<anonymous> (/app/node_modules/sharp/lib/index.js:6:15)
#50 15.59     at Module._compile (node:internal/modules/cjs/loader:1521:14)
#50 15.59 
#50 15.59 Node.js v20.20.0
#50 ERROR: process "node --expose-gc ./src/backend/index --run-diagnostics --config-path=/app/diagnostics-config.json --Server-Log-level=silly" did not complete successfully: exit code: 1
------
 > [linux/arm/v7 runtime 9/9] RUN ["node", "--expose-gc", "./src/backend/index", "--run-diagnostics", "--config-path=/app/diagnostics-config.json", "--Server-Log-level=silly"]:
15.59     at Module._compile (node:internal/modules/cjs/loader:1521:14)
15.59     at Module._extensions..js (node:internal/modules/cjs/loader:1623:10)
15.59     at Module.load (node:internal/modules/cjs/loader:1266:32)
15.59     at Module._load (node:internal/modules/cjs/loader:1091:12)
15.59     at Module.require (node:internal/modules/cjs/loader:1289:19)
15.59     at require (node:internal/modules/helpers:182:18)
15.59     at Object.<anonymous> (/app/node_modules/sharp/lib/index.js:6:15)
15.59     at Module._compile (node:internal/modules/cjs/loader:1521:14)
15.59 
15.59 Node.js v20.20.0
------
WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
Dockerfile.build:86
--------------------
  84 |     
  85 |     # Diagnostics
  86 | >>> RUN ["node", "--expose-gc", "./src/backend/index", "--run-diagnostics", "--config-path=/app/diagnostics-config.json", "--Server-Log-level=silly"]
  87 |     
  88 |     HEALTHCHECK --interval=40s --timeout=30s --retries=3 --start-period=60s \
--------------------
ERROR: failed to build: failed to solve: process "node --expose-gc ./src/backend/index --run-diagnostics --config-path=/app/diagnostics-config.json --Server-Log-level=silly" did not complete successfully: exit code: 1
Error: buildx failed with: ERROR: failed to build: failed to solve: process "node --expose-gc ./src/backend/index --run-diagnostics --config-path=/app/diagnostics-config.json --Server-Log-level=silly" did not complete successfully: exit code: 1

I'm not sure if that is an issue. I think we can just drop it.

It seems that it prevents build on arm/v7:

#45 [linux/arm/v7 runtime 7/9] RUN npm install --omit=dev && npm cache clean --force
#45 118.6 
#45 118.6 added 296 packages, and audited 297 packages in 2m
#45 118.6 
#45 118.6 54 packages are looking for funding
#45 118.6   run `npm fund` for details
#45 118.8 
#45 118.8 5 vulnerabilities (1 moderate, 4 high)
#45 118.8 
#45 118.8 To address all issues, run:
#45 118.8   npm audit fix --force
#45 118.8 
#45 118.8 Run `npm audit` for details.
#45 118.8 npm notice
#45 118.8 npm notice New major version of npm available! 10.8.2 -> 11.9.0
#45 118.8 npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.9.0
#45 118.8 npm notice To update run: npm install -g npm@11.9.0
#45 118.8 npm notice
#45 130.3 npm warn using --force Recommended protections disabled.
#45 DONE 132.8s

#49 [linux/arm/v7 runtime 8/9] RUN mkdir -p /app/data/config   /app/data/db   /app/data/images   /app/data/tmp
#49 DONE 0.1s

#50 [linux/arm/v7 runtime 9/9] RUN ["node", "--expose-gc", "./src/backend/index", "--run-diagnostics", "--config-path=/app/diagnostics-config.json", "--Server-Log-level=silly"]
#50 15.59 /app/node_modules/sharp/lib/sharp.js:121
#50 15.59   throw new Error(help.join('\n'));
#50 15.59   ^
#50 15.59 
#50 15.59 Error: Could not load the "sharp" module using the linuxmusl-arm runtime
#50 15.59 Possible solutions:
#50 15.59 - Manually install libvips >= 8.16.1
#50 15.59 - Add experimental WebAssembly-based dependencies:
#50 15.59     npm install --cpu=wasm32 sharp
#50 15.59     npm install @img/sharp-wasm32
#50 15.59 - Consult the installation documentation:
#50 15.59     See https://sharp.pixelplumbing.com/install
#50 15.59     at Object.<anonymous> (/app/node_modules/sharp/lib/sharp.js:121:9)
#50 15.59     at Module._compile (node:internal/modules/cjs/loader:1521:14)
#50 15.59     at Module._extensions..js (node:internal/modules/cjs/loader:1623:10)
#50 15.59     at Module.load (node:internal/modules/cjs/loader:1266:32)
#50 15.59     at Module._load (node:internal/modules/cjs/loader:1091:12)
#50 15.59     at Module.require (node:internal/modules/cjs/loader:1289:19)
#50 15.59     at require (node:internal/modules/helpers:182:18)
#50 15.59     at Object.<anonymous> (/app/node_modules/sharp/lib/constructor.js:10:1)
#50 15.59     at Module._compile (node:internal/modules/cjs/loader:1521:14)
#50 15.59     at Module._extensions..js (node:internal/modules/cjs/loader:1623:10)
#50 15.59     at Module.load (node:internal/modules/cjs/loader:1266:32)
#50 15.59     at Module._load (node:internal/modules/cjs/loader:1091:12)
#50 15.59     at Module.require (node:internal/modules/cjs/loader:1289:19)
#50 15.59     at require (node:internal/modules/helpers:182:18)
#50 15.59     at Object.<anonymous> (/app/node_modules/sharp/lib/index.js:6:15)
#50 15.59     at Module._compile (node:internal/modules/cjs/loader:1521:14)
#50 15.59 
#50 15.59 Node.js v20.20.0
#50 ERROR: process "node --expose-gc ./src/backend/index --run-diagnostics --config-path=/app/diagnostics-config.json --Server-Log-level=silly" did not complete successfully: exit code: 1
------
 > [linux/arm/v7 runtime 9/9] RUN ["node", "--expose-gc", "./src/backend/index", "--run-diagnostics", "--config-path=/app/diagnostics-config.json", "--Server-Log-level=silly"]:
15.59     at Module._compile (node:internal/modules/cjs/loader:1521:14)
15.59     at Module._extensions..js (node:internal/modules/cjs/loader:1623:10)
15.59     at Module.load (node:internal/modules/cjs/loader:1266:32)
15.59     at Module._load (node:internal/modules/cjs/loader:1091:12)
15.59     at Module.require (node:internal/modules/cjs/loader:1289:19)
15.59     at require (node:internal/modules/helpers:182:18)
15.59     at Object.<anonymous> (/app/node_modules/sharp/lib/index.js:6:15)
15.59     at Module._compile (node:internal/modules/cjs/loader:1521:14)
15.59 
15.59 Node.js v20.20.0
------
WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
Dockerfile.build:86
--------------------
  84 |     
  85 |     # Diagnostics
  86 | >>> RUN ["node", "--expose-gc", "./src/backend/index", "--run-diagnostics", "--config-path=/app/diagnostics-config.json", "--Server-Log-level=silly"]
  87 |     
  88 |     HEALTHCHECK --interval=40s --timeout=30s --retries=3 --start-period=60s \
--------------------
ERROR: failed to build: failed to solve: process "node --expose-gc ./src/backend/index --run-diagnostics --config-path=/app/diagnostics-config.json --Server-Log-level=silly" did not complete successfully: exit code: 1
Error: buildx failed with: ERROR: failed to build: failed to solve: process "node --expose-gc ./src/backend/index --run-diagnostics --config-path=/app/diagnostics-config.json --Server-Log-level=silly" did not complete successfully: exit code: 1

I'm not sure if that is an issue. I think we can just drop it.

I have reverted the npm install to see if it makes any difference, doubt they will but to keep the change smaller as i cant test on anything non amd64 atm.

@HuwSy HuwSy closed this by deleting the head repository Feb 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants