Mark Feldhousen
Mark Feldhousen
Thank you @aaclayton, the container does use the `--noupdate` flag as you suggested: https://github.com/felddy/foundryvtt-docker/blob/b8334b27487f0132799331f8453576aace8fca63/Dockerfile#L97-L100 The issue here is that I can only patch the languages that exist when the distribution...
I just [fielded a question on Discord](https://discord.com/channels/170995199584108546/605545525374353429/1179103777459019807) about applying the suggested fix for this issue to the [FoundryVTT container](https://github.com/felddy/foundryvtt-docker) I maintain. I thought I'd post my reply here for anyone...
> I think adding this script may warrant a bump of the patch portion of the version as well. Bumped in: 1654c50
Slightly better than it used to be: 21 of 20 ```text ❱ awslimitchecker VPC/Rules per network ACL (limit 20) CRITICAL: acl-028c31e0a1b550987=21 WARNING: acl-0e75636adb082380a=17, acl-0481ed40691e46b63=17, acl-040b742905929c6b0=17, acl-08e56f35e9ef52f22=17, acl-0608d9024408de7e6=17, acl-061e36710cd994924=17, acl-0b5df1c6f1ebe7cb6=17, acl-09bdfded65eb44001=17,...
Wow. This is a great bug! Thanks for the extra diagnostics on the hashes. I know exactly why this is happening. FoundryVTT made the decision to not use semver a...
The log messages are from FoundryVTT, not the container's tooling. Are there any errors or warnings in the startup of the container? Please post the verbose logs of the container...
Thanks for the extra logs. I just wanted to confirm that the container is able to download and install the release from Cloudflare. So it has connectivity there. You said...
This is very similar to: - https://github.com/felddy/foundryvtt-docker/issues/565 Are you running PiHole or doing any other bespoke DNS filtering? Container network mode? Try adding this to your environment variables: ```bash NODE_DEBUG=http,net...
This looks like a proxy is mucking something up. ```console FoundryVTT | HTTP 120: SERVER new http connection FoundryVTT | HTTP 120: SERVER socketOnParserExecute NaN FoundryVTT | HTTP 120: parse...
> I tried connecting directly to the server's local IP with the exposed port. That should remove the proxy from the equation, right?: That should remove the proxy between you...