docker container startet nicht unter proxmox 9
-
hi,
hab einen frischen server mit proxmox 9 aufgesetzt. darunter docker-ce installiert, nun iobroker per docker-compose.yml gestartet.docker-compose.yml:
services: iobroker: container_name: iobroker image: buanet/iobroker hostname: iobroker restart: always ports: - "8081:8081" volumes: - iobrokerdata:/opt/iobroker environment: - TZ=Europe/Berlin - DEBUG=yes # devices: # - /dev/ttyUSB0:/dev/ttyUSB0 volumes: iobrokerdata:der start über
docker compose up -d
schlägt aber fehl. output:iobroker | -------------------------------------------------------------------------------- iobroker | ----- Step 5 of 5: ioBroker Startup ----- iobroker | -------------------------------------------------------------------------------- iobroker | iobroker | Starting ioBroker... iobroker | iobroker | ##### #### ### ## # iobroker.js-controller log output # ## ### #### ##### iobroker | Error while calling "getconf CLK_TCK" Error: spawn /bin/sh EACCES iobroker | at ChildProcess._handle.onexit (node:internal/child_process:285:19) iobroker | at onErrorNT (node:internal/child_process:483:16) iobroker | at process.processTicksAndRejections (node:internal/process/task_queues:90:21) { iobroker | errno: -13, iobroker | code: 'EACCES', iobroker | syscall: 'spawn /bin/sh', iobroker | path: '/bin/sh', iobroker | spawnargs: [ '-c', 'getconf CLK_TCK' ], iobroker | cmd: 'getconf CLK_TCK' iobroker | } iobroker | read ENOTCONN iobroker | Error: read ENOTCONN iobroker | at tryReadStart (node:net:716:20) iobroker | at Socket._read (node:net:731:5) iobroker | at Readable.read (node:internal/streams/readable:739:12) iobroker | at Socket.read (node:net:785:39) iobroker | at new Socket (node:net:494:12) iobroker | at Object.Socket (node:net:363:41) iobroker | at createSocket (node:internal/child_process:335:14) iobroker | at ChildProcess.spawn (node:internal/child_process:450:23) iobroker | at spawn (node:child_process:786:9) iobroker | at Object.execFile (node:child_process:349:17) iobroker | read ENOTCONN iobroker | Error: read ENOTCONN iobroker | at tryReadStart (node:net:716:20) iobroker | at Socket._read (node:net:731:5) iobroker | at Readable.read (node:internal/streams/readable:739:12) iobroker | at Socket.read (node:net:785:39) iobroker | at new Socket (node:net:494:12) iobroker | at Object.Socket (node:net:363:41) iobroker | at createSocket (node:internal/child_process:335:14) iobroker | at ChildProcess.spawn (node:internal/child_process:450:23) iobroker | at spawn (node:child_process:786:9) iobroker | at Object.execFile (node:child_process:349:17) iobroker | read ENOTCONN iobroker | Error: read ENOTCONN iobroker | at tryReadStart (node:net:716:20) iobroker | at Socket._read (node:net:731:5) iobroker | at Readable.read (node:internal/streams/readable:739:12) iobroker | at Socket.read (node:net:785:39) iobroker | at new Socket (node:net:494:12) iobroker | at Object.Socket (node:net:363:41) iobroker | at createSocket (node:internal/child_process:335:14) iobroker | at ChildProcess.spawn (node:internal/child_process:450:23) iobroker | at spawn (node:child_process:786:9) iobroker | at Object.execFile (node:child_process:349:17)hat jemand eine idee, was das ist? hab schon gesucht, aber nichts passendes gefunden.
gruß,
andre -
hier das komplette startlog:
iobroker | -------------------------------------------------------------------------------- iobroker | ------------------------- 2025-09-24 16:42:38 ------------------------- iobroker | -------------------------------------------------------------------------------- iobroker | ----- ----- iobroker | ----- ██╗ ██████╗ ██████╗ ██████╗ ██████╗ ██╗ ██╗ ███████╗ ██████╗ ----- iobroker | ----- ██║ ██╔═══██╗ ██╔══██╗ ██╔══██╗ ██╔═══██╗ ██║ ██╔╝ ██╔════╝ ██╔══██╗ ----- iobroker | ----- ██║ ██║ ██║ ██████╔╝ ██████╔╝ ██║ ██║ █████╔╝ █████╗ ██████╔╝ ----- iobroker | ----- ██║ ██║ ██║ ██╔══██╗ ██╔══██╗ ██║ ██║ ██╔═██╗ ██╔══╝ ██╔══██╗ ----- iobroker | ----- ██║ ╚██████╔╝ ██████╔╝ ██║ ██║ ╚██████╔╝ ██║ ██╗ ███████╗ ██║ ██║ ----- iobroker | ----- ╚═╝ ╚═════╝ ╚═════╝ ╚═╝ ╚═╝ ╚═════╝ ╚═╝ ╚═╝ ╚══════╝ ╚═╝ ╚═╝ ----- iobroker | ----- ----- iobroker | ----- Welcome to your ioBroker Docker container! ----- iobroker | ----- Startupscript is now running! ----- iobroker | ----- Please be patient! ----- iobroker | -------------------------------------------------------------------------------- iobroker | iobroker | -------------------------------------------------------------------------------- iobroker | ----- System Information ----- iobroker | ----- arch: x86_64 ----- iobroker | ----- hostname: iobroker ----- iobroker | ----- ----- iobroker | ----- Version Information ----- iobroker | ----- image: v11.0.0 ----- iobroker | ----- build: 20250912.234259 ----- iobroker | ----- node: v22.19.0 ----- iobroker | ----- npm: 10.9.3 ----- iobroker | ----- ----- iobroker | ----- Environment Variables ----- iobroker | ----- DEBUG: yes ----- iobroker | ----- SETGID: 1000 ----- iobroker | ----- SETUID: 1000 ----- iobroker | -------------------------------------------------------------------------------- iobroker | iobroker | -------------------------------------------------------------------------------- iobroker | ----- Step 1 of 5: Preparing Container ----- iobroker | -------------------------------------------------------------------------------- iobroker | iobroker | iobroker | iobroker | -------------------------------------------------------------------------------- iobroker | ----- Step 2 of 5: Detecting ioBroker Installation ----- iobroker | -------------------------------------------------------------------------------- iobroker | iobroker | Existing installation of ioBroker detected in "/opt/iobroker". iobroker | iobroker | -------------------------------------------------------------------------------- iobroker | ----- Step 3 of 5: Checking ioBroker Installation ----- iobroker | -------------------------------------------------------------------------------- iobroker | iobroker | (Re)setting permissions (This might take a while! Please be patient!)... Done. iobroker | iobroker | Checking database connection... Done. iobroker | iobroker | Hostname in ioBroker matches the hostname of this container. iobroker | No action required. iobroker | iobroker | -------------------------------------------------------------------------------- iobroker | ----- Step 4 of 5: Applying Special Settings ----- iobroker | -------------------------------------------------------------------------------- iobroker | iobroker | Some adapters have special requirements/ settings which can be activated by the use of environment variables. iobroker | For more information see ioBroker Docker image docs (https://docs.buanet.de/iobroker-docker-image/docs/). iobroker | iobroker | -------------------------------------------------------------------------------- iobroker | ----- Step 5 of 5: ioBroker Startup ----- iobroker | -------------------------------------------------------------------------------- iobroker | iobroker | Starting ioBroker... iobroker | iobroker | ##### #### ### ## # iobroker.js-controller log output # ## ### #### ##### iobroker | Error while calling "getconf CLK_TCK" Error: spawn /bin/sh EACCES iobroker | at ChildProcess._handle.onexit (node:internal/child_process:285:19) iobroker | at onErrorNT (node:internal/child_process:483:16) iobroker | at process.processTicksAndRejections (node:internal/process/task_queues:90:21) { iobroker | errno: -13, iobroker | code: 'EACCES', iobroker | syscall: 'spawn /bin/sh', iobroker | path: '/bin/sh', iobroker | spawnargs: [ '-c', 'getconf CLK_TCK' ], iobroker | cmd: 'getconf CLK_TCK' iobroker | } [...] -
@astrakid sagte in docker container startet nicht unter proxmox 9:
das liegt höchst wahrscheinlich daran, das du dadurch eine verschachtelte virtualisierung erzeugst. also die virtualisierung in einer virtualisierung hat weniger rechte.
schau mal ob du da was dazu in proxmox konfigurieren kannst. -
@oliverio sagte in docker container startet nicht unter proxmox 9:
h eine verschachtelte virtualisierung erzeugst. also die virtualisierung in einer virtualisierung
innerhalb des OS habe ich docker direkt installiert und gestartet, nicht in einem LXC oder einer VM. und als benutzer root (ich weiß, nicht optimal).
-
Da fehlt mir die Beschreibung des "Zwischenbaus"
Auf einem Proxmox System sollte man nur LXC-Container und virtuelle Maschinen installieren...
docker-ce direkt auf dem PVE Muttersystem installieren schafft Verdruss...
Wenn Du eine VM aufgesetzt hast oder einen LXC Container, in dem dann wiederum docker läuft:
Was ist denn die Ausgabe, wenn Du als normaler User in der VM / dem LXC dies hier eintippst:
marrtin@iobroker-test-sicher:/opt/iobroker$ getconf CLK_TCK 100 -
@martinp sagte in docker container startet nicht unter proxmox 9:
getconf CLK_TCK
funktioniert sogar aus dem iobroker-container heraus:
-
@astrakid Du hast also docker direkt im Hypervisor installiert?
Etwas direkt im Hypervisor installieren ist schlechter Stil ...
https://www.reddit.com/r/Proxmox/comments/1cluao4/whats_the_best_way_to_run_docker_in_proxmox/
EDIT: ich sehe gerade "root"
Unter welchem User ist denn das Installationsskript gelaufen?
-
@martinp sagte in docker container startet nicht unter proxmox 9:
https://www.reddit.com/r/Proxmox/comments/1cluao4/whats_the_best_way_to_run_docker_in_proxmox/
im link steht was von, das es die netzwerkfähigkeiten von proxmox zerstört.
wahrscheinlich wenn man irgendwas mit macvlan oder ipvlan verwenden will, da dann ein eigener treiber genutzt wird.ich dachte proxmox sei ein geschlossenes system/betriebssystem. da dann noch was auf oberster ebene zu installieren dürfte doch dann beim nächsten update ebenfalls schwierigkeiten geben.
