Repository navigation
Breaking change in behavior on node:25-alpine docker image. #2310
Description
We have got some type of changed behavior in two version of the docker image
node:
Broken version: sha256:3f162243a45e30f6b20f80255779785789e142bec7b1d5d3b431f31d5b3610f6 (released 2025-11-13)
Working version: sha256:7e467cc5aa91c87e94f93c4608cf234ca24aac3ec941f7f3db207367ccccdd11
In the broken version we get:
ERROR in SecurityError: Cannot initialize local storage without a --localstorage-file path
Activity
[-]Changed behavior in node:25-alpine docker image.[/-][+]Breaking change in behavior on node:25-alpine docker image.[/+]yosifkit commentedon Nov 13, 2025
Could you provide more information about how to reproduce the failure? Perhaps a minimal reproducer and some environment information (e.g.
docker version,uname -a).The difference between the two images is just the
NODE_VERSION=25.2.0: bf78d76...a364e16#diff-0967fa49a8a2e87942d43011cc34bf127b12879486850aba1fb8bfc45c0896b1L3-R3(Git commit ids gathered from the annotations on the OCI image indexes 25.2.0 and 25.1.0)
jesper-at-antirio commentedon Nov 13, 2025
Hi..
I have been able to cleanup our project, the issue I want to highlight are depending on if I using
25-alpine image with sha256:7e467cc5aa91c87e94f93c4608cf234ca24aac3ec941f7f3db207367ccccdd11
or
25-alpine image with sha256:3f162243a45e30f6b20f80255779785789e142bec7b1d5d3b431f31d5b3610f6
I get different result, when using alpine with hash 3f16, I will get "ERROR in SecurityError: Cannot initialize local storage without a
--localstorage-filepath" error on the build step in the attached docker file.And with the other older version of 25-alpine (7e46) the build is succeding.
The change in how localstorage is handled, it may of course been indented and my error is as simple I was not using like 25.2.0-alpine
ui-app.zip
Edit:
Seem this is relevant nodejs/node#60351 so maybe guessing this is intended and my error was not using 25.1.0-alpine...
sxa commentedon Feb 13, 2026
@jesper-at-antirio On the basis of your last edit are you happy for this issue to be closed now as it appears to be working as designed?
jesper-at-antirio commentedon Feb 13, 2026
Yes, you may close it, still bit surprised of the breaking change between 25.2.0 and 25.1.0