starred/uptime-kuma
1
0
Fork 0
mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00
Code Issues 754 Projects Packages Wiki Activity

Launching Uptime Kuma in Portainer fails #1831

New issue
Closed
opened 2026-02-28 02:34:03 -05:00 by deekerman · 16 comments
deekerman commented 2026-02-28 02:34:03 -05:00
Owner
Copy link

Originally created by @dtenney on GitHub (Jan 26, 2023).

⚠️ Please verify that this bug has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

Trying to launch Uptime Kuma within Portainer using the default docker-composer.yml and getting an error message:

==> Performing startup jobs and maintenance tasks
changed ownership of '/app/data' from 1001:users to 0:0
==> Starting application with user 0 group 0
Welcome to Uptime Kuma
node:internal/modules/cjs/loader:998

throw err;
^
Error: Cannot find module 'dayjs'
Require stack:

  • /app/server/server.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:995:15)
    at Function.Module._load (node:internal/modules/cjs/loader:841:27)
    at Module.require (node:internal/modules/cjs/loader:1067:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at Object. (/app/server/server.js:9:15)
    at Module._compile (node:internal/modules/cjs/loader:1165:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1219:10)
    at Module.load (node:internal/modules/cjs/loader:1043:32)
    at Function.Module._load (node:internal/modules/cjs/loader:878:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) {
    code: 'MODULE_NOT_FOUND',
    requireStack: [ '/app/server/server.js' ]
    }

Docker compose:
version: '3.3'

services:
uptime-kuma:
image: louislam/uptime-kuma:1
container_name: uptime-kuma
volumes:
- ./uptime-kuma-data:/app/data
ports:
- 3001:3001 # :
restart: always

🐻 Uptime-Kuma Version

1.19.6

💻 Operating System and Arch

Debian GNU/Linux 11

🌐 Browser

Google Chrome Version 109.0.5414.119

🐋 Docker Version

20.10.23

🟩 NodeJS Version

No response

Originally created by @dtenney on GitHub (Jan 26, 2023). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem Trying to launch Uptime Kuma within Portainer using the default docker-composer.yml and getting an error message: ==> Performing startup jobs and maintenance tasks changed ownership of '/app/data' from 1001:users to 0:0 ==> Starting application with user 0 group 0 Welcome to Uptime Kuma node:internal/modules/cjs/loader:998 throw err; ^ Error: Cannot find module 'dayjs' Require stack: - /app/server/server.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:995:15) at Function.Module._load (node:internal/modules/cjs/loader:841:27) at Module.require (node:internal/modules/cjs/loader:1067:19) at require (node:internal/modules/cjs/helpers:103:18) at Object.<anonymous> (/app/server/server.js:9:15) at Module._compile (node:internal/modules/cjs/loader:1165:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1219:10) at Module.load (node:internal/modules/cjs/loader:1043:32) at Function.Module._load (node:internal/modules/cjs/loader:878:12) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) { code: 'MODULE_NOT_FOUND', requireStack: [ '/app/server/server.js' ] } Docker compose: version: '3.3' services: uptime-kuma: image: louislam/uptime-kuma:1 container_name: uptime-kuma volumes: - ./uptime-kuma-data:/app/data ports: - 3001:3001 # <Host Port>:<Container Port> restart: always ### 🐻 Uptime-Kuma Version 1.19.6 ### 💻 Operating System and Arch Debian GNU/Linux 11 ### 🌐 Browser Google Chrome Version 109.0.5414.119 ### 🐋 Docker Version 20.10.23 ### 🟩 NodeJS Version _No response_
deekerman 2026-02-28 02:34:03 -05:00
  • closed this issue
  • added the
    Stale
    help
         labels
deekerman commented 2026-02-28 02:34:11 -05:00
Author
Owner
Copy link

@Anexgohan commented on GitHub (Jan 27, 2023):

use this docker-compose.yml

version: '3.3'
services:
  uptime-kuma:
    image: 'louislam/uptime-kuma:1'
    container_name: uptime-kuma
    restart: always
    ports:
      - '3001:3001'
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock    #for docker host support in uptime-kuma
      - /path/to/wherever/uptime-kuma:/app/data    #config and data location for uptime-kuma, also used below to "docker volume create uptime-kuma"
#following is equivelent to docker command "docker volume create uptime-kuma" ,note that "uptime-kuma" is also binded above location
volumes:
  uptime-kuma:
@Anexgohan commented on GitHub (Jan 27, 2023): use this docker-compose.yml ``` version: '3.3' services: uptime-kuma: image: 'louislam/uptime-kuma:1' container_name: uptime-kuma restart: always ports: - '3001:3001' volumes: - /var/run/docker.sock:/var/run/docker.sock #for docker host support in uptime-kuma - /path/to/wherever/uptime-kuma:/app/data #config and data location for uptime-kuma, also used below to "docker volume create uptime-kuma" #following is equivelent to docker command "docker volume create uptime-kuma" ,note that "uptime-kuma" is also binded above location volumes: uptime-kuma: ```
deekerman commented 2026-02-28 02:34:11 -05:00
Author
Owner
Copy link

@louislam commented on GitHub (Jan 27, 2023):

Error: Cannot find module 'dayjs'

That is weird, it shouldn't happen on a container.

I am guessing, the image maybe corrupted?

Try to pull it again:
docker pull louislam/uptime-kuma:1

@louislam commented on GitHub (Jan 27, 2023): > Error: Cannot find module 'dayjs' That is weird, it shouldn't happen on a container. I am guessing, the image maybe corrupted? Try to pull it again: `docker pull louislam/uptime-kuma:1`
deekerman commented 2026-02-28 02:34:11 -05:00
Author
Owner
Copy link

@dtenney commented on GitHub (Jan 27, 2023):

I get the same error with the suggested docker pull and new compose file. I'm wondering if it has something to do with my system's architecture, aarch64. I see several call outs to armv7 throughout the git repo and the error seems to state that the dependencies are not being installed.

@dtenney commented on GitHub (Jan 27, 2023): I get the same error with the suggested docker pull and new compose file. I'm wondering if it has something to do with my system's architecture, aarch64. I see several call outs to armv7 throughout the git repo and the error seems to state that the dependencies are not being installed.
deekerman commented 2026-02-28 02:34:11 -05:00
Author
Owner
Copy link

@louislam commented on GitHub (Jan 27, 2023):

Tested on Oracle Cloud's arm64 machine, it is working.

Because all files should be ready inside the container/image, it should not happen. It is the weird part.

I think you should go inside and see what is inside the image:

docker run --rm -it louislam/uptime-kuma:1 bash
cd /app/
ls
cd /app/node_modules
ls # See if dayjs there

image

@louislam commented on GitHub (Jan 27, 2023): Tested on Oracle Cloud's arm64 machine, it is working. Because all files should be ready inside the container/image, it should not happen. It is the weird part. I think you should go inside and see what is inside the image: ```bash docker run --rm -it louislam/uptime-kuma:1 bash cd /app/ ls cd /app/node_modules ls # See if dayjs there ``` ![image](https://user-images.githubusercontent.com/1336778/215135077-d1326fdb-3310-4103-a555-4d511de4d612.png)
deekerman commented 2026-02-28 02:34:11 -05:00
Author
Owner
Copy link

@dtenney commented on GitHub (Jan 27, 2023):

The dayjs module is there. Running the server.js command directly gives me the error.

root@f32c06877c11:~# cd /app/
root@f32c06877c11:/app# ls
config	data  db  dist	docker	extra  index.html  node_modules  package-lock.json  package.json  public  server  src
root@f32c06877c11:/app# cd /app/node_modules 
root@f32c06877c11:/app/node_modules# ls dayjs
CHANGELOG.md  LICENSE  README.md  dayjs.min.js	esm  index.d.ts  locale  locale.json  package.json  plugin

root@f32c06877c11:/app# node server/server.js 
Welcome to Uptime Kuma
node:internal/modules/cjs/loader:998
  throw err;
  ^

Error: Cannot find module 'dayjs'
Require stack:
- /app/server/server.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:995:15)
    at Function.Module._load (node:internal/modules/cjs/loader:841:27)
    at Module.require (node:internal/modules/cjs/loader:1067:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at Object.<anonymous> (/app/server/server.js:9:15)
    at Module._compile (node:internal/modules/cjs/loader:1165:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1219:10)
    at Module.load (node:internal/modules/cjs/loader:1043:32)
    at Function.Module._load (node:internal/modules/cjs/loader:878:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/app/server/server.js' ]
}
root@f32c06877c11:/app#
@dtenney commented on GitHub (Jan 27, 2023): The dayjs module is there. Running the server.js command directly gives me the error. ``` root@f32c06877c11:~# cd /app/ root@f32c06877c11:/app# ls config data db dist docker extra index.html node_modules package-lock.json package.json public server src root@f32c06877c11:/app# cd /app/node_modules root@f32c06877c11:/app/node_modules# ls dayjs CHANGELOG.md LICENSE README.md dayjs.min.js esm index.d.ts locale locale.json package.json plugin ``` ``` root@f32c06877c11:/app# node server/server.js Welcome to Uptime Kuma node:internal/modules/cjs/loader:998 throw err; ^ Error: Cannot find module 'dayjs' Require stack: - /app/server/server.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:995:15) at Function.Module._load (node:internal/modules/cjs/loader:841:27) at Module.require (node:internal/modules/cjs/loader:1067:19) at require (node:internal/modules/cjs/helpers:103:18) at Object.<anonymous> (/app/server/server.js:9:15) at Module._compile (node:internal/modules/cjs/loader:1165:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1219:10) at Module.load (node:internal/modules/cjs/loader:1043:32) at Function.Module._load (node:internal/modules/cjs/loader:878:12) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) { code: 'MODULE_NOT_FOUND', requireStack: [ '/app/server/server.js' ] } root@f32c06877c11:/app# ```
deekerman commented 2026-02-28 02:34:11 -05:00
Author
Owner
Copy link

@louislam commented on GitHub (Jan 27, 2023):

Too strange, what is your hardware? Is your Debian downloaded from official?

@louislam commented on GitHub (Jan 27, 2023): Too strange, what is your hardware? Is your Debian downloaded from official?
deekerman commented 2026-02-28 02:34:11 -05:00
Author
Owner
Copy link

@dtenney commented on GitHub (Jan 27, 2023):

It's an Asustor NAS AS3304T. I've posted a similar question on their forums to see if anyone else has seen something similar. https://forum.asustor.com/viewtopic.php?f=184&t=13643&p=45944#p45944

To add, I have other docker containers running directly from the command line and portainer as well.

@dtenney commented on GitHub (Jan 27, 2023): It's an Asustor NAS AS3304T. I've posted a similar question on their forums to see if anyone else has seen something similar. https://forum.asustor.com/viewtopic.php?f=184&t=13643&p=45944#p45944 To add, I have other docker containers running directly from the command line and portainer as well.
deekerman commented 2026-02-28 02:34:11 -05:00
Author
Owner
Copy link

@dtenney commented on GitHub (Jan 27, 2023):

I tried running npm by itself and got this error:

root@f32c06877c11:/app# npm
node:internal/modules/cjs/loader:998
  throw err;
  ^

Error: Cannot find module '../lib/cli.js'
Require stack:
- /usr/local/bin/npm
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:995:15)
    at Function.Module._load (node:internal/modules/cjs/loader:841:27)
    at Module.require (node:internal/modules/cjs/loader:1067:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at Object.<anonymous> (/usr/local/bin/npm:2:1)
    at Module._compile (node:internal/modules/cjs/loader:1165:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1219:10)
    at Module.load (node:internal/modules/cjs/loader:1043:32)
    at Function.Module._load (node:internal/modules/cjs/loader:878:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/usr/local/bin/npm' ]
}
@dtenney commented on GitHub (Jan 27, 2023): I tried running npm by itself and got this error: ``` root@f32c06877c11:/app# npm node:internal/modules/cjs/loader:998 throw err; ^ Error: Cannot find module '../lib/cli.js' Require stack: - /usr/local/bin/npm at Function.Module._resolveFilename (node:internal/modules/cjs/loader:995:15) at Function.Module._load (node:internal/modules/cjs/loader:841:27) at Module.require (node:internal/modules/cjs/loader:1067:19) at require (node:internal/modules/cjs/helpers:103:18) at Object.<anonymous> (/usr/local/bin/npm:2:1) at Module._compile (node:internal/modules/cjs/loader:1165:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1219:10) at Module.load (node:internal/modules/cjs/loader:1043:32) at Function.Module._load (node:internal/modules/cjs/loader:878:12) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) { code: 'MODULE_NOT_FOUND', requireStack: [ '/usr/local/bin/npm' ] } ```
deekerman commented 2026-02-28 02:34:11 -05:00
Author
Owner
Copy link

@louislam commented on GitHub (Jan 27, 2023):

I guess it maybe a OS issue or a kernel issue.

You should try the node.js image directly.

docker run --rm -it node:16-buster-slim bash
@louislam commented on GitHub (Jan 27, 2023): I guess it maybe a OS issue or a kernel issue. You should try the node.js image directly. ``` docker run --rm -it node:16-buster-slim bash ```
deekerman commented 2026-02-28 02:34:11 -05:00
Author
Owner
Copy link

@dtenney commented on GitHub (Jan 27, 2023):

I am able to run npm on the host itself but it looks like an old version that gets installed.

root@media-nas:/volume1 # npm -v
6.4.1

@dtenney commented on GitHub (Jan 27, 2023): I am able to run npm on the host itself but it looks like an old version that gets installed. root@media-nas:/volume1 # npm -v 6.4.1
deekerman commented 2026-02-28 02:34:11 -05:00
Author
Owner
Copy link

@dtenney commented on GitHub (Jan 27, 2023):

Further digging, I get the error when I use an updated node version v18.x. The base Debian packages run node and npm but uptime kuma doesn't install due to the age of the repository versions. Working to recompile on the host itself and see if that allows me to run the newer version.

@dtenney commented on GitHub (Jan 27, 2023): Further digging, I get the error when I use an updated node version v18.x. The base Debian packages run node and npm but uptime kuma doesn't install due to the age of the repository versions. Working to recompile on the host itself and see if that allows me to run the newer version.
deekerman commented 2026-02-28 02:34:11 -05:00
Author
Owner
Copy link

@louislam commented on GitHub (Jan 27, 2023):

Further digging, I get the error when I use an updated node version v18.x. The base Debian packages run node and npm but uptime kuma doesn't install due to the age of the repository versions. Working to recompile on the host itself and see if that allows me to run the newer version.

So maybe my guessing is correct, it may be a kernel bug of your device. You should provide reproduce steps to Asustor team.

Before that, make sure your Debian's packages are fully updated to the lastest versions.

@louislam commented on GitHub (Jan 27, 2023): > Further digging, I get the error when I use an updated node version v18.x. The base Debian packages run node and npm but uptime kuma doesn't install due to the age of the repository versions. Working to recompile on the host itself and see if that allows me to run the newer version. So maybe my guessing is correct, it may be a kernel bug of your device. You should provide reproduce steps to Asustor team. Before that, make sure your Debian's packages are fully updated to the lastest versions.
deekerman commented 2026-02-28 02:34:11 -05:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Apr 28, 2023):

We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.

@github-actions[bot] commented on GitHub (Apr 28, 2023): We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.
deekerman commented 2026-02-28 02:34:11 -05:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Apr 30, 2023):

This issue was closed because it has been stalled for 2 days with no activity.

@github-actions[bot] commented on GitHub (Apr 30, 2023): This issue was closed because it has been stalled for 2 days with no activity.
deekerman commented 2026-02-28 02:34:11 -05:00
Author
Owner
Copy link

@dynumo commented on GitHub (Feb 23, 2025):

It's unfortunate this still seems to be an issue with asustor 2 years later. Having the same problem. Do you recall if you found a solution @dtenney ?

@dynumo commented on GitHub (Feb 23, 2025): It's unfortunate this still seems to be an issue with asustor 2 years later. Having the same problem. Do you recall if you found a solution @dtenney ?
deekerman commented 2026-02-28 02:34:11 -05:00
Author
Owner
Copy link

@dtenney commented on GitHub (Feb 23, 2025):

After sending in a request to asustor support and getting nowhere, I decided to run uptime-kuma on a raspberry pi. It also seems that a large chunk of the "apps" asustor provides were created by one person a long time ago and they are all defunct. Example: https://www.asustor.com/en/app_central/app_detail?id=1455&type=

@dtenney commented on GitHub (Feb 23, 2025): After sending in a request to asustor support and getting nowhere, I decided to run uptime-kuma on a raspberry pi. It also seems that a large chunk of the "apps" asustor provides were created by one person a long time ago and they are all defunct. Example: https://www.asustor.com/en/app_central/app_detail?id=1455&type=
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
npm-update
3.0.X
dev-better-auth
copilot/remove-password-complexity-requirements
2.2.X
copilot/sub-pr-6355
1.23.X
api-via-socketio-client
2.1.3
2.1.2
2.1.1
2.1.0
2.1.0-beta.3
2.1.0-beta.2
2.1.0-beta.1
2.1.0-beta.0
2.0.2
2.0.1
1.23.17
2.0.0
2.0.0-beta.4
2.0.0-beta.3
2.0.0-beta.2
2.0.0-beta.2-temp
2.0.0-beta.1
1.23.16
2.0.0-beta.0
1.23.15
1.23.14
1.23.13
1.23.12
1.23.11
1.23.10
1.23.9
1.23.8
1.23.7
1.23.6
1.23.5
1.23.5-beta.0
1.23.4
1.23.3
1.23.2
1.23.1
1.23.0
1.23.0-beta.1
1.23.0-beta.0
1.22.1
1.22.0
1.22.0-beta.0
1.21.3
1.21.2
1.21.2-beta.0
1.21.1
1.21.0
1.21.0-beta.1
1.21.0-beta.0
1.20.2
1.20.1
1.20.0
1.20.0-beta.0
1.19.6
1.19.5
1.19.4
1.19.3
1.19.2
1.19.1
1.19.0
1.19.0-beta.2
1.19.0-beta.1
1.19.0-beta.0
1.18.5
1.18.4
1.18.3
1.18.2
1.18.1
1.18.0
1.18.0-beta.0
1.17.1
1.17.0
1.17.0-beta.1
1.17.0-beta.0
1.16.1
1.16.0
1.16.0-beta.0
1.15.1
1.15.0
1.15.0-beta.1
1.14.1
1.15.0-beta.0
1.14.0
1.14.0-beta.2
1.13.2
1.14.0-beta.1
1.14.0-beta.0
1.13.1
1.13.0
1.13.0-beta.2
1.13.0-beta.1
1.13.0-beta.0
1.12.1
1.12.0
1.11.4
1.11.3
1.11.2
1.11.1
1.11.0
1.10.2
1.10.1
1.10.0
1.9.2
1.9.1
1.9.0
1.8.0
1.7.3
1.7.2
1.7.1
1.7.0
1.6.3
1.6.2
1.6.1
1.6.0
1.5.3
1.5.2
1.5.1
1.5.0
1.3.2
1.3.1
1.3.0
1.2.0
1.1.0
1.0.10
1.0.9
1.0.8
1.0.7
1.0.6
1.0.5
1.0.4
1.0.3
1.0.2
1.0.1
1.0.0
Labels
Clear labels   
A:accessibility

   
A:api

   
A:cert-expiry

   
A:core

   
A:dashboard

   
A:deployment

   
A:documentation

   
A:domain expiry

   
A:incidents

   
A:maintenance

   
A:metrics

   
A:monitor

   
A:notifications

   
A:reports

   
A:settings

   
A:status-page

   
A:ui/ux

   
A:user-management

   
Stale

   
ai-slop

   
blocked

   
blocked-upstream

   
bug

   
cannot-reproduce

   
dependencies

   
discussion

   
duplicate

   
feature-request

   
feature-request

   
good first issue

   
hacktoberfest

   
help

   
help wanted

   
house keeping

   
invalid

   
invalid-format

   
invalid-format

   
question

   
releaseblocker 🚨

   
security

   
spam

   
type:enhance-existing

   
type:new

   
wontfix
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#1831
No description provided.