Unable to start Docker container after Portainer auto-update

[zsgcgrs]

Description

Node.js v22.16.0
/usr/src/app/start-docker.sh:3
[ ! -z "${USER_UID}" ] && usermod -u ${USER_UID} node || echo "No USER_UID specified, leaving 1000"
^^^^^^^^^^^^^
SyntaxError: Unexpected string
at wrapSafe (node:internal/modules/cjs/loader:1662:18)
at Module._compile (node:internal/modules/cjs/loader:1704:20)
at Object..js (node:internal/modules/cjs/loader:1895:10)
at Module.load (node:internal/modules/cjs/loader:1465:32)
at Function._load (node:internal/modules/cjs/loader:1282:12)
at TracingChannel.traceSync (node:diagnostics_channel:322:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:235:24)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:171:5)
at node:internal/main/run_main_module:36:49

TriliumNext Version

v0.94.0

What operating system are you using?

Windows

What is your setup?

Local (no sync)

Operating System Version

docker

Error logs

Node.js v22.16.0
/usr/src/app/start-docker.sh:3
[ ! -z "${USER_UID}" ] && usermod -u ${USER_UID} node || echo "No USER_UID specified, leaving 1000"
^^^^^^^^^^^^^
SyntaxError: Unexpected string
at wrapSafe (node:internal/modules/cjs/loader:1662:18)
at Module._compile (node:internal/modules/cjs/loader:1704:20)
at Object..js (node:internal/modules/cjs/loader:1895:10)
at Module.load (node:internal/modules/cjs/loader:1465:32)
at Function._load (node:internal/modules/cjs/loader:1282:12)
at TracingChannel.traceSync (node:diagnostics_channel:322:14)
at wrapModuleLoad (node:internal/modules/cjs/loader:235:24)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:171:5)
at node:internal/main/run_main_module:36:49

[photoncody]

Hey, I just submitted this issue myself! Beat me to it.

[zsgcgrs]

Haha, I want to add that I upgraded from v0.93.0 and it couldn't start, but I redeployed a v0.94.0 and it started normally, so there should be a compatibility issue.

[eliandoran]

Very interesting problem.

@photoncody , @zsgcgrs , are you using some kind of auto-upgrade mechanism that caused this issue for you?
Indeed, running the Docker container from scratch doesn't cause any issue.

[zsgcgrs]

use portainer

[photoncody]

@eliandoran I'm using a system called cosmos server https://cosmos-cloud.io/

It auto-upgraded TriliumNext to latest version in the same timeframe as @zsgcgrs.

So far the only thing that fixed it was pinning the version to v0.93.0.

[perfectra1n]

Hey @photoncody and @zsgcgrs, are you able to share some images of the configuration for the container within your Cosmos/Portainer?

It’s strange, something is causing Node to run the “start-docker.sh” file - instead of Bash/Sh. Any pictures/images/information you could share about its configuration or how it’s deployed would help a ton :)

I’m running it via Portainer and Kubernetes, and can’t get the issue to immediately reproduce…

[zsgcgrs]

services:
notes:
container_name: TriliumNext
network_mode: bridge
restart: always
environment:
- TZ=Asia/Shanghai
- UMASK=000
- TRILIUM_NO_UPLOAD_LIMIT=1
- TRILIUM_DATA_DIR=/home/node/trilium-data
ports:
- '6611:8080/tcp'
volumes:
- '/home/docker/TriliumNext:/home/node/trilium-data:rw'
- '/home/docker/TriliumNext/backup:/home/node/trilium-data/backup:rw'
image: 'triliumnext/notes:v0.93.0'

Hope this will help you !

[zsgcgrs]

The startup command in v0.94.0 is sh ./start-docker.sh, which is different from v0.93.0. The problem may be here.

[zsgcgrs]

Haha, an interesting thing happened. I wanted to change compose to v0.94.0 and then change the startup command. However, after I changed compose to v0.94.0, the startup command became normal and became 'sh' './start-docker.sh', so the container started normally.

[kazzyUK]

** Edit **

so looking at the example compose above, i didnt have UMASK=000.. so added that and redid docker compose up -d and now the site loads up and i can login and see my notes.

not sure if that fixed it, or if it was because i was doing at the command line rather than using Portainer

---

I've upgrade from V0.93 to V0.94 doing a Docker image Recreate (via portainer) and it now errors with the same message as posted above.

my CMD is listed as ./start-docker.sh so how do we get the SH added to the front of the CMD command?

will a v0.94.01 get posted out soon?

[perfectra1n]

Can you share some images and information about how your Docker is deployed? Can you share your entire Docker Compose file, or how you're deploying it?

Something is overriding the Docker entrypoint command to be ./start-docker.sh instead of sh ./start-docker.sh as you mentioned it. The entrypoint is correct in the container image:

So something must be overriding it...

[kazzyUK]

Sure here my compose file.

trilium:
container_name: trilium
image: triliumnext/notes:latest
environment:
- TZ=europe/london
- UMASK=000
security_opt:
- no-new-privileges:true
ports:
- 4532:8080
volumes:
- ./trilium/data:/home/node/trilium-data
- /etc/timezone:/etc/timezone:ro
- /etc/localtime:/etc/localtime:ro
restart: unless-stopped
networks:
- notes

I think maybe just running from the command line

docker-compose down and then docker-compose up -d fixed it.. not convinced it was adding the UMASK Line.

before i was using Portainer and using the Recreate button and enable the Pull new version option.