Is it possible to block auto-update when using an old version tag ?

[nemonobody777]

Hello,

I'm trying to setup a FoundryVTT v11.315.1 instance, using the felddy/foundryvtt:11.315.1 image. However, when starting the container auto-update himself to version 12.324 (please see the logs below). Is it possible to block this auto-update behaviour to keep a v11.315.1 running ?

What I've tried so far :

• setup a FOUNDRY_VERSION env to value "11.315.1" -> no effect
• removing all version related envs -> no effect

Logs at startup :

> User-Agent: curl/8.5.0 (felddy/foundryvtt:11.315.1)

> Accept: */*

> 

{ [5 bytes data]

* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):

{ [230 bytes data]

* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):

{ [230 bytes data]

* old SSL session ID is stale, removing

{ [5 bytes data]

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0< HTTP/2 200 

< date: Sat, 25 May 2024 10:23:15 GMT

< content-type: application/x-zip-compressed

< content-length: 231745734

< etag: "cd353d440f587e48a00eed8038a2f4a6-28"

< last-modified: Wed, 22 May 2024 16:11:30 GMT

< vary: Accept-Encoding

< cache-control: max-age=14400

< cf-cache-status: MISS

< accept-ranges: bytes

< server: cloudflare

< cf-ray: 8894cf155be57832-CDG

< 

{ [39104 bytes data]

 35  221M   35 79.4M    0     0  67.7M      0  0:00:03  0:00:01  0:00:02 67.7M

 81  221M   81  180M    0     0  82.4M      0  0:00:02  0:00:02 --:--:-- 82.4M

100  221M  100  221M    0     0  86.5M      0  0:00:02  0:00:02 --:--:-- 86.5M

* Connection #0 to host r2.foundryvtt.com left intact

Entrypoint | 2024-05-25 10:23:17 | [info] Installing Foundry Virtual Tabletop 12.324

Entrypoint | 2024-05-25 10:23:17 | [debug] Checking mime-type of release file.

Entrypoint | 2024-05-25 10:23:17 | [debug] Found mime-type: application/zip

Entrypoint | 2024-05-25 10:23:17 | [debug] Extracting release file.

Entrypoint | 2024-05-25 10:23:22 | [debug] Installation completed.

Entrypoint | 2024-05-25 10:23:22 | [info] Preserving release archive file in cache.

Entrypoint | 2024-05-25 10:23:22 | [debug] CONTAINER_CACHE_SIZE is not set. Skipping cache cleanup.

Entrypoint | 2024-05-25 10:23:22 | [debug] Patching GUI update and configuration messages.

Entrypoint | 2024-05-25 10:23:22 | [info] Not modifying existing installation license key.

Entrypoint | 2024-05-25 10:23:22 | [info] Setting data directory permissions.

Entrypoint | 2024-05-25 10:23:22 | [debug] Setting ownership of /data to 1035:65538.

Entrypoint | 2024-05-25 10:23:22 | [debug] Completed setting directory permissions.

Entrypoint | 2024-05-25 10:23:22 | [info] Starting launcher with uid:gid as 1035:65538.

Entrypoint | 2024-05-25 10:23:22 | [debug] Waiting for child pid: 87 to exit.

Launcher | 2024-05-25 10:23:22 | [debug] Ensuring /data/Config directory exists.

Launcher | 2024-05-25 10:23:22 | [info] Generating options.json file.

Launcher | 2024-05-25 10:23:22 | [info] Setting 'Admin Access Key'.

Launcher | 2024-05-25 10:23:22 | [info] Starting Foundry Virtual Tabletop.

FoundryVTT | 2024-05-25 10:23:24 | [info] Running on Node.js - Version 18.19.0

FoundryVTT | 2024-05-25 10:23:24 | [info] Foundry Virtual Tabletop - Version 12 Build 324

FoundryVTT | 2024-05-25 10:23:24 | [info] User Data Directory - "/data"

FoundryVTT | 2024-05-25 10:23:24 | [info] Application Options:

{

  "awsConfig": null,

  "compressSocket": false,

  "compressStatic": false,

  "cssTheme": "foundry",

  "fullscreen": false,

  "hostname": "foundry.xxxxxxx",

  "hotReload": false,

  "language": "fr.fr-core",

  "localHostname": "foundry.xxxxxxxx",

  "passwordSalt": null,

  "port": 30000,

  "protocol": null,

  "proxyPort": 443,

  "proxySSL": true,

  "routePrefix": null,

  "sslCert": "******/cert.pem",

  "sslKey": "******/privkey.pem",

  "telemetry": false,

  "updateChannel": "stable",

  "upnp": false,

  "upnpLeaseDuration": null,

  "world": null,

  "adminPassword": "••••••••••••••••",

  "deleteNEDB": false,

  "noBackups": false,

  "serviceConfig": null

}

FoundryVTT | 2024-05-25 10:23:24 | [info] Software license verification succeeded

FoundryVTT | 2024-05-25 10:23:24 | [info] Server started and listening on port 30000

Thanks a lot for your help.

[felddy]

The important information is at the start of the logs. This will contain detailed information about versions and the environment variables that are set. The logs you've posted are starting at the download. If you update your comment to include the start of the logs, I'll be able to help more.

[nemonobody777]

Thanks a lot, you lead me on the right track ! I am deploying on a Synology NAS, and was managing the containers on Portainer instead of the default Synology Docker manager. For an unknown reason, each time I removed the FOUNDRY_VERSION env on Portainer, it was reset to 12.184 by the Syno Docker Manager, which was the cause of the upgrade. Indeed, the env used were displayed at the start of the logs, which did not appear in Portainer because of the restart of the container after the upgrade to 12.184.

Thanks again for your help, and all your work on this image.