Container Stopped Working! #124

ratzofftyoya · 2020-12-08T17:43:44Z

ratzofftyoya
Dec 8, 2020

💬 Questions and Help

Hi there! Not sure what happened. My container was working totally fine, including after pulling 0.7.8, but then it stopped working. On restart (including after removing image), I get the following in an endless loop.:

Entrypoint | 2020-12-08 17:42:26 | [info] Starting felddy/foundryvtt container v0.7.8
Entrypoint | 2020-12-08 17:42:26 | [info] Foundry Virtual Tabletop 0.7.8 is installed.
Entrypoint | 2020-12-08 17:42:26 | [info] Not modifying existing installation license key.
Entrypoint | 2020-12-08 17:42:26 | [info] Setting data directory permissions.
Entrypoint | 2020-12-08 17:42:28 | [info] Starting launcher with uid:gid as foundry:foundry.

felddy · 2020-12-08T18:10:56Z

felddy
Dec 8, 2020
Maintainer

Sorry you're having this problem. I haven't had this behavior reported before. I'll see what I can do to help.

I'll need some additional information to help diagnose:

How are you running the Docker container? e.g.; docker-compose, docker CLI, ...

Could you please provide the container's configuration file, or command used to start it.

Please run this command:

docker inspect --format='{{range $k, $v := .Config.Labels}}
    {{- printf "%s = \"%s\"\n" $k $v -}} {{end}}' \
    felddy/foundryvtt:release

Paste the results here:

Run the container with CONTAINER_VERBOSE set to true,and paste any useful
log output here:

Make sure not to post any credentials, or other sensitive information.

0 replies

ratzofftyoya · 2020-12-08T18:43:51Z

ratzofftyoya
Dec 8, 2020
Author

Thanks so much for your response!

How are you running the Docker container? e.g.; docker-compose, docker CLI, ...

Running with docker-compose (as I was previously)

Could you please provide the container's configuration file, or command used to start it.

Here is the compose script:

foundry:
    image: felddy/foundryvtt:latest
    init: true
    restart: "unless-stopped"
    networks:
      - traefik_proxy
    volumes:
      - type: bind
        source: /mnt/server/data/foundry/foundrydata
        target: /data
    environment:
      - FOUNDRY_PASSWORD=[mypassword]
      - FOUNDRY_USERNAME=[myusername]
      - CONTAINTER_VERBOSE=true
      - CONTAINER_PATCHES=/data/containerpatches #ADDED THIS AFTER PROBLEMS STARTED TO SEE IF IT MIGHT HELP
      - FOUNDRY_LICENSE_KEY=[mylicense key]  #ADDED THIS AFTER PROBLEMS STARTED TO SEE IF IT MIGHT HELP
    ports:
      - target: "30000"
        published: "30000"
        protocol: tcp
    labels: #THE SETUP BELOW IS IDENTICAL (BUT FOR THE "FOUNDRY" BITS, OF COURSE) TO MY OTHER WORKING CONTAINERS
      - "traefik.enable=true"
      ## HTTP Routers
      - "traefik.http.routers.foundry-rtr.entrypoints=https"
      - "traefik.http.routers.foundry-rtr.rule=HostHeader(`play.$DOMAINNAME`)"
      ## Middlewares
      - "traefik.http.routers.foundry-rtr.middlewares=chain-no-auth@file"
      ## HTTP Services
      - "traefik.http.routers.foundry-rtr.service=foundry-svc"
      - "traefik.http.services.foundry-svc.loadbalancer.server.port=30000"

Please run this command:

docker inspect --format='{{range $k, $v := .Config.Labels}}
    {{- printf "%s = \"%s\"\n" $k $v -}} {{end}}' \
    felddy/foundryvtt:release

Paste the results here:

com.foundryvtt.version = "0.7.8"
org.opencontainers.image.authors = "[email protected]"
org.opencontainers.image.created = "2020-12-04T17:18:28Z"
org.opencontainers.image.description = "An easy-to-deploy Dockerized Foundry Virtual Tabletop server."
org.opencontainers.image.licenses = "MIT"
org.opencontainers.image.revision = "d79ba13ebc52df9b3b0f189381789b934d5f26d7"
org.opencontainers.image.source = "https://github.com/felddy/foundryvtt-docker.git"
org.opencontainers.image.title = "foundryvtt-docker"
org.opencontainers.image.url = "https://github.com/felddy/foundryvtt-docker"
org.opencontainers.image.vendor = "Geekpad"
org.opencontainers.image.version = "0.7.8"

Run the container with CONTAINER_VERBOSE set to true,and paste any useful
log output here:

Here is the full log until the endless loop starts:

Entrypoint | 2020-12-08 18:39:49 | [info] Starting felddy/foundryvtt container v0.7.8
Entrypoint | 2020-12-08 18:39:49 | [info] No Foundry Virtual Tabletop installation detected.
Entrypoint | 2020-12-08 18:39:49 | [info] Using FOUNDRY_USERNAME and FOUNDRY_PASSWORD to authenticate.
Authenticate | 2020-12-08 18:39:49 | [info] Requesting CSRF tokens from https://foundryvtt.com
Authenticate | 2020-12-08 18:39:50 | [info] Logging in as: [REDACTED]
Authenticate | 2020-12-08 18:39:52 | [info] Successfully logged in as: [REDACTED]
Entrypoint | 2020-12-08 18:39:52 | [info] Using authenticated credentials to download release.
ReleaseURL | 2020-12-08 18:39:52 | [info] Fetching S3 pre-signed release URL for 0.7.8...
Entrypoint | 2020-12-08 18:39:53 | [info] Downloading Foundry Virtual Tabletop release.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0  115M    0 68213    0     0  48139      0  0:41:46  0:00:01  0:41:45 48105
  0  115M    0  882k    0     0   351k      0  0:05:34  0:00:02  0:05:32  351k
  6  115M    6 8033k    0     0  2364k      0  0:00:49  0:00:03  0:00:46 2364k
 19  115M   19 22.7M    0     0  5192k      0  0:00:22  0:00:04  0:00:18 5191k
 30  115M   30 34.9M    0     0  6660k      0  0:00:17  0:00:05  0:00:12 7314k
 43  115M   43 49.6M    0     0  7937k      0  0:00:14  0:00:06  0:00:08  9.9M
 53  115M   53 62.1M    0     0  8627k      0  0:00:13  0:00:07  0:00:06 12.5M
 66  115M   66 76.1M    0     0  9314k      0  0:00:12  0:00:08  0:00:04 13.7M
 77  115M   77 88.9M    0     0  9706k      0  0:00:12  0:00:09  0:00:03 13.5M
 88  115M   88  102M    0     0   9.8M      0  0:00:11  0:00:10  0:00:01 13.4M
100  115M  100  115M    0     0  10.1M      0  0:00:11  0:00:11 --:--:-- 13.4M
Entrypoint | 2020-12-08 18:40:04 | [info] Installing Foundry Virtual Tabletop 0.7.8
Entrypoint | 2020-12-08 18:40:06 | [info] Using CONTAINER_PATCHES: /data/containerpatches
Entrypoint | 2020-12-08 18:40:06 | [warn] Container patches directory not found.
Entrypoint | 2020-12-08 18:40:06 | [info] Not modifying existing installation license key.
Entrypoint | 2020-12-08 18:40:06 | [info] Setting data directory permissions.
Entrypoint | 2020-12-08 18:40:08 | [info] Starting launcher with uid:gid as foundry:foundry.
Entrypoint | 2020-12-08 18:40:09 | [info] Starting felddy/foundryvtt container v0.7.8
Entrypoint | 2020-12-08 18:40:09 | [info] Foundry Virtual Tabletop 0.7.8 is installed.
Entrypoint | 2020-12-08 18:40:09 | [info] Not modifying existing installation license key.
Entrypoint | 2020-12-08 18:40:09 | [info] Setting data directory permissions.
Entrypoint | 2020-12-08 18:40:12 | [info] Starting launcher with uid:gid as foundry:foundry.
Entrypoint | 2020-12-08 18:40:13 | [info] Starting felddy/foundryvtt container v0.7.8
Entrypoint | 2020-12-08 18:40:13 | [info] Foundry Virtual Tabletop 0.7.8 is installed.
Entrypoint | 2020-12-08 18:40:13 | [info] Not modifying existing installation license key.
Entrypoint | 2020-12-08 18:40:13 | [info] Setting data directory permissions.
Entrypoint | 2020-12-08 18:40:15 | [info] Starting launcher with uid:gid as foundry:foundry.
Entrypoint | 2020-12-08 18:40:16 | [info] Starting felddy/foundryvtt container v0.7.8
Entrypoint | 2020-12-08 18:40:16 | [info] Foundry Virtual Tabletop 0.7.8 is installed.
Entrypoint | 2020-12-08 18:40:16 | [info] Not modifying existing installation license key.
Entrypoint | 2020-12-08 18:40:16 | [info] Setting data directory permissions.
Entrypoint | 2020-12-08 18:40:19 | [info] Starting launcher with uid:gid as foundry:foundry.
Entrypoint | 2020-12-08 18:40:20 | [info] Starting felddy/foundryvtt container v0.7.8
Entrypoint | 2020-12-08 18:40:20 | [info] Foundry Virtual Tabletop 0.7.8 is installed.
Entrypoint | 2020-12-08 18:40:20 | [info] Not modifying existing installation license key.
Entrypoint | 2020-12-08 18:40:20 | [info] Setting data directory permissions.

Note also that I've recursively chmodded the data folder to 0777.

0 replies

felddy · 2020-12-08T19:06:40Z

felddy
Dec 8, 2020
Maintainer

You've got a typo in your environment variables: CONTAINTER_VERBOSE should be CONTAINER_VERBOSE.

After fixing that could you repost the logs. You should see [debug] entries.

0 replies

ratzofftyoya · 2020-12-08T19:23:53Z

ratzofftyoya
Dec 8, 2020
Author

Thank you @felddy ! Unfortunately, the [debug] text is not helping much. Here is all of it (loop resumes after this with no further debug entries):

Entrypoint | 2020-12-08 19:17:58 | [info] Starting felddy/foundryvtt container v0.7.8
Entrypoint | 2020-12-08 19:17:58 | [info] No Foundry Virtual Tabletop installation detected.
Entrypoint | 2020-12-08 19:17:58 | [info] Using FOUNDRY_USERNAME and FOUNDRY_PASSWORD to authenticate.
Authenticate | 2020-12-08 19:17:58 | [debug] Saving cookies to: cookiejar.json
Authenticate | 2020-12-08 19:17:58 | [info] Requesting CSRF tokens from https://foundryvtt.com
Authenticate | 2020-12-08 19:17:58 | [debug] Fetching: https://foundryvtt.com
Authenticate | 2020-12-08 19:17:59 | [info] Logging in as: [REDACTED]
Authenticate | 2020-12-08 19:17:59 | [debug] Fetching: https://foundryvtt.com/auth/login/
Authenticate | 2020-12-08 19:18:01 | [debug] Community URL: /community/[REDACTED]
Authenticate | 2020-12-08 19:18:01 | [info] Successfully logged in as: [REDACTED]
Entrypoint | 2020-12-08 19:18:01 | [info] Using authenticated credentials to download release.
ReleaseURL | 2020-12-08 19:18:01 | [debug] Loading cookies from: cookiejar.json
ReleaseURL | 2020-12-08 19:18:01 | [info] Fetching S3 pre-signed release URL for 0.7.8...
ReleaseURL | 2020-12-08 19:18:01 | [debug] Fetching: https://foundryvtt.com/releases/download?version=0.7.8&platform=linux
ReleaseURL | 2020-12-08 19:18:02 | [debug] S3 presigned URL: https://foundryvtt.s3.amazonaws.com/releases/0.7.8/foundryvtt-0.7.8.zip?AWSAccessKeyId=AKIAISZIIE42YLQZKLEQ&Signature=XdaaefXr3YeXCkl9OStIM3STi7A%3D&Expires=1607455382

6 replies

felddy Dec 8, 2020
Maintainer

I added some additional logging and published an image for you to test. Please change your docker-compose.yml to pull felddy/foundryvtt:improvement-launcher_logging, and restart it.

foundry:
    image: felddy/foundryvtt:improvement-launcher_logging

The logs should look like this:

foundry_1  | Entrypoint | 2020-12-08 14:51:05 | [info] Not modifying existing installation license key.
foundry_1  | Entrypoint | 2020-12-08 14:51:05 | [info] Setting data directory permissions.
foundry_1  | Entrypoint | 2020-12-08 14:51:19 | [info] Starting launcher with uid:gid as 501:20.
foundry_1  | Launcher | 2020-12-08 14:51:19 | [info] Ensuring /data/Config directory exists.

This should shed some light on the error causing the container to die.

ratzofftyoya Dec 9, 2020
Author

Thanks so much for the image! I think the culprit is below, though I don't know how to fix it. To answer your previous question, I'm running this on x64 Debian on a system I'm using as a headless server/NAS.

Launcher | 2020-12-09 00:32:30 | [debug] Ensuring /data/Config directory exists.
Launcher | 2020-12-09 00:32:30 | [info] Generating options.json file.
./launcher.sh: line 28: can't create /data/Config/options.json: nonexistent directory

Note that the Config directory was created with drwxrwsr-x+ perms. Should I start the image with my docker-friendly PUID and GUID rather than what appears to be the default (foundry:foundry)?

ratzofftyoya Dec 9, 2020
Author

One update! Each time I create a new directory for testing, the Foundry launcher or something else within the container successfully creates Config, successfully creates license.json, and successfully populates that with a single line.

ratzofftyoya Dec 9, 2020
Author

Update: I set my parent "data" directory, which previously housed the "foundrydata" folder as the new "/data" bind for the container. Seems to have worked like a charm. But it also reset the owner and group for that directory to " 421." That user doesn't seem to be found by the system. Not sure what's going on...

felddy Dec 9, 2020
Maintainer

It sounds like you've made progress.

You can change the server's uid:gid by setting the FOUNDRY_UID and FOUNDRY_GID environment variables.

See: https://github.com/felddy/foundryvtt-docker#optional

ratzofftyoya · 2020-12-09T15:58:48Z

ratzofftyoya
Dec 9, 2020
Author

I have! I basically figured out a workaround by setting a parent category as the data category. But it doesn’t really explain the behavior and also I continue to be concerned about this user “421” taking over my folders. Any ideas?

…

On Wed, Dec 9, 2020 at 10:22 PM Mark Feldhousen ***@***.***> wrote: It sounds like you've made progress. You can change the server's uid:gid by setting the FOUNDRY_UID and FOUNDRY_GID environment variables. See: https://github.com/felddy/foundryvtt-docker#optional — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#124 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASBPMUD5S4IAETLSXGBLV5TST6BYTANCNFSM4USNLSPA> .

1 reply

felddy Dec 9, 2020
Maintainer

When the container starts up it chowns the /data directory:

foundryvtt-docker/src/entrypoint.sh

Lines 201 to 203 in 1ffb74e

    
           # ensure the permissions are set correctly 
        
           log "Setting data directory permissions." 
        
           chown -R "${FOUNDRY_UID:-foundry}:${FOUNDRY_GID:-foundry}" /data

You can change the uid:gid used by setting the FOUNDRY_UID and FOUNDRY_GID environment variables. By default it is using 421:421.

See: https://github.com/felddy/foundryvtt-docker#optional

ratzofftyoya · 2020-12-09T16:13:38Z

ratzofftyoya
Dec 9, 2020
Author

I see! Any thoughts of why the previous install failed (seemingly for permission issues)?

…

On Thu, Dec 10, 2020 at 12:04 AM Mark Feldhousen ***@***.***> wrote: When the container starts up it chowns the /data directory: https://github.com/felddy/foundryvtt-docker/blob/1ffb74e312e03c4f6c5661288aa07cc996f5787e/src/entrypoint.sh#L201-L203 You can change the uid:gid used by setting the FOUNDRY_UID and FOUNDRY_GID environment variables. By default it is using 421:421. See: https://github.com/felddy/foundryvtt-docker#optional — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#124 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASBPMUEJDJX4Y7BLXPGJX7DST6NXJANCNFSM4USNLSPA> .

1 reply

felddy Dec 9, 2020
Maintainer

It most certainly was a permission error. I'm still perplexed by the log that shows the config directory existing, and then the next line says it doesn't. That doesn't make any sense unless there was a race condition with another external process. (The container itself only has one process.)

The reason I asked about the NAS is that some Docker installs have constraints on bind source locations. This can result in a similar behavior.

ratzofftyoya · 2020-12-09T17:18:16Z

ratzofftyoya
Dec 9, 2020
Author

Hm...But it was working before. I'll monitor for more poor behavior!

…

On Thu, Dec 10, 2020 at 1:09 AM Mark Feldhousen ***@***.***> wrote: It most certainly was a permission error. I'm still perplexed by the log that shows the config directory existing, and then the next line says it doesn't. That doesn't make any sense unless there was a race condition with another external process. (The container itself only has one process.) The reason I asked about the NAS is that some Docker installs have constraints on bind source locations. This can result in a similar behavior. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#124 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASBPMUGA623BHNR65WWJCNDST6VNFANCNFSM4USNLSPA> .

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Container Stopped Working! #124

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 7 comments 8 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Container Stopped Working! #124

ratzofftyoya Dec 8, 2020

💬 Questions and Help

Replies: 7 comments · 8 replies

felddy Dec 8, 2020 Maintainer

ratzofftyoya Dec 8, 2020 Author

felddy Dec 8, 2020 Maintainer

ratzofftyoya Dec 8, 2020 Author

felddy Dec 8, 2020 Maintainer

ratzofftyoya Dec 9, 2020 Author

ratzofftyoya Dec 9, 2020 Author

ratzofftyoya Dec 9, 2020 Author

felddy Dec 9, 2020 Maintainer

ratzofftyoya Dec 9, 2020 Author

felddy Dec 9, 2020 Maintainer

ratzofftyoya Dec 9, 2020 Author

felddy Dec 9, 2020 Maintainer

ratzofftyoya Dec 9, 2020 Author

ratzofftyoya
Dec 8, 2020

Replies: 7 comments 8 replies

felddy
Dec 8, 2020
Maintainer

ratzofftyoya
Dec 8, 2020
Author

felddy
Dec 8, 2020
Maintainer

ratzofftyoya
Dec 8, 2020
Author

felddy Dec 8, 2020
Maintainer

ratzofftyoya Dec 9, 2020
Author

ratzofftyoya Dec 9, 2020
Author

ratzofftyoya Dec 9, 2020
Author

felddy Dec 9, 2020
Maintainer

ratzofftyoya
Dec 9, 2020
Author

felddy Dec 9, 2020
Maintainer

ratzofftyoya
Dec 9, 2020
Author

felddy Dec 9, 2020
Maintainer

ratzofftyoya
Dec 9, 2020
Author