Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to start 2.0.0-beta.0 inside podman container #5406

Closed
2 tasks done
thimomulder opened this issue Dec 4, 2024 · 4 comments
Closed
2 tasks done

Unable to start 2.0.0-beta.0 inside podman container #5406

thimomulder opened this issue Dec 4, 2024 · 4 comments
Labels

Comments

@thimomulder
Copy link

thimomulder commented Dec 4, 2024

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

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

Unable to start the beta version of Uptime-Kuma using the following command: sudo podman run -d --replace --restart=always -p 3001:3001 -v ~/uptime-kuma-beta/data:/app/data --name uptime-kuma-beta louislam/uptime-kuma:beta

📝 Error Message(s) or Log

Welcome to Uptime Kuma
Your Node.js version: 20.18.0
2024-12-04T13:42:28Z [SERVER] INFO: Env: production
2024-12-04T13:42:29Z [SERVER] INFO: Uptime Kuma Version: 2.0.0-beta.0
2024-12-04T13:42:29Z [SERVER] INFO: Loading modules
2024-12-04T13:42:29Z [SERVER] INFO: Creating express and socket.io instance
2024-12-04T13:42:29Z [SERVER] INFO: Server Type: HTTP
Trace: Error: EACCES: permission denied, mkdir 'data/upload/'
    at Object.mkdirSync (node:fs:1371:26)
    at Database.initDataDir (/app/server/database.js:146:16)
    at /app/server/server.js:173:14
    at Object.<anonymous> (/app/server/server.js:1624:3)
    at Module._compile (node:internal/modules/cjs/loader:1469:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1548:10)
    at Module.load (node:internal/modules/cjs/loader:1288:32)
    at Module._load (node:internal/modules/cjs/loader:1104:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:174:12)
    at node:internal/main/run_main_module:28:49 {
  errno: -13,
  code: 'EACCES',
  syscall: 'mkdir',
  path: 'data/upload/'
}
    at process.unexpectedErrorHandler (/app/server/server.js:1872:13)
    at process.emit (node:events:519:28)
    at emitUnhandledRejection (node:internal/process/promises:250:13)
    at throwUnhandledRejectionsMode (node:internal/process/promises:385:19)
    at processPromiseRejections (node:internal/process/promises:470:17)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:32)
If you keep encountering errors, please report to https://github.com/louislam/uptime-kuma/issues

🐻 Uptime-Kuma Version

v2.0.0.0-beta.0

💻 Operating System and Arch

RHEL 9

🌐 Browser

not used

🖥️ Deployment Environment

not used

@CommanderStorm
Copy link
Collaborator

Trace: Error: EACCES: permission denied, mkdir 'data/upload/'

What are the permissions of data/upload

@thimomulder
Copy link
Author

thimomulder commented Dec 5, 2024

The folder data/upload/ doesn't excist. The folder data is created by me with the permissions set at 0755

@almereyda
Copy link

If you're running on a SELinux-enabled system, such as RHEL/Fedora, you will also need to specify to unshare the SELinux label for the container to be able to access the volume.

This is done with amending the :z/:Z flag to volume mount declarations.

Also see:

@thimomulder
Copy link
Author

@almereyda Adding the :z/:Z flag fixed the problem thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants