Container failed to start because of dependency #24

Closed
opened 2025-11-13 11:47:49 -06:00 by GiteaMirror · 1 comment
Owner

Originally created by @Royalflash5220 on GitHub (Jan 20, 2025).

Im using a Hetzner Debian 12 VPS on the latest update to host pangolin.
I took a snapshot of my current VPS, which i use for monitoring my public services and took it as a base for this as a testing environment.
The snapshot had wireguard and docker installed with 2 containers running (uptimekuma, nginx proxy manager).

While installing i got this error at the end:

Starting containers...
[+] Pulling 3/3
 ✔ gerbil Pulled                                                                                                     1.1s
 ✔ traefik Pulled                                                                                                    1.1s
 ✔ pangolin Pulled                                                                                                   1.1s
[+] Running 1/1
 ✘ Container pangolin  Error                                                                                         0.5s
dependency failed to start: container pangolin is unhealthy
Failed to start containers using docker-compose command

Could this be cause by having wireguard already preinstalled?

The only errors i could find in the docker log was this, which is weird, because my password meets this criteria:

> @fosrl/pangolin@1.0.0-beta.7 start
> NODE_OPTIONS=--enable-source-maps NODE_ENV=development ENVIRONMENT=prod sh -c 'node dist/migrations.mjs && node dist/server.mjs'

Starting migrations from version 1.0.0-beta.7
All migrations completed successfully
/app/server/lib/config.ts:222
            throw new Error(`Invalid configuration file: ${errors}`);
                  ^

Error: Invalid configuration file: Validation error: Your password must meet the following conditions:
at least one uppercase English letter,
at least one lowercase English letter,
at least one digit,
at least one special character. at "users.server_admin.password"
    at Config.loadConfig (/app/server/lib/config.ts:222:19)
    at new Config (/app/server/lib/config.ts:146:14)
    at <anonymous> (/app/server/lib/config.ts:334:23)

Node.js v20.18.1`

This is only my second github issue so please let me know, if i missed any information you need.
Thanks in advance!

Originally created by @Royalflash5220 on GitHub (Jan 20, 2025). Im using a Hetzner Debian 12 VPS on the latest update to host pangolin. I took a snapshot of my current VPS, which i use for monitoring my public services and took it as a base for this as a testing environment. The snapshot had wireguard and docker installed with 2 containers running (uptimekuma, nginx proxy manager). While installing i got this error at the end: ``` Starting containers... [+] Pulling 3/3 ✔ gerbil Pulled 1.1s ✔ traefik Pulled 1.1s ✔ pangolin Pulled 1.1s [+] Running 1/1 ✘ Container pangolin Error 0.5s dependency failed to start: container pangolin is unhealthy Failed to start containers using docker-compose command ``` Could this be cause by having wireguard already preinstalled? The only errors i could find in the docker log was this, which is weird, because my password meets this criteria: ``` > @fosrl/pangolin@1.0.0-beta.7 start > NODE_OPTIONS=--enable-source-maps NODE_ENV=development ENVIRONMENT=prod sh -c 'node dist/migrations.mjs && node dist/server.mjs' Starting migrations from version 1.0.0-beta.7 All migrations completed successfully /app/server/lib/config.ts:222 throw new Error(`Invalid configuration file: ${errors}`); ^ Error: Invalid configuration file: Validation error: Your password must meet the following conditions: at least one uppercase English letter, at least one lowercase English letter, at least one digit, at least one special character. at "users.server_admin.password" at Config.loadConfig (/app/server/lib/config.ts:222:19) at new Config (/app/server/lib/config.ts:146:14) at <anonymous> (/app/server/lib/config.ts:334:23) Node.js v20.18.1` ``` This is only my second github issue so please let me know, if i missed any information you need. Thanks in advance!
Author
Owner

@Royalflash5220 commented on GitHub (Jan 20, 2025):

Answer:
Yes, it was the wireguard server that couldnt bind to the port.

@Royalflash5220 commented on GitHub (Jan 20, 2025): Answer: Yes, it was the wireguard server that couldnt bind to the port.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#24