Mark Feldhousen

@dependabot rebase

FWIW, I'm seeing this same behavior. GitHub Actions run: - https://github.com/felddy/foundryvtt-docker/actions/runs/4600601595/jobs/8128005604#step:6:1 Calling step: ```yml - name: Generate SBOM uses: anchore/sbom-action@422cb34a0f8b599678c41b21163ea6088edb2624 with: artifact-name: ${{ steps.clean.outputs.image_archive_name_stem }}-sbom.spdx.json file: ${{ steps.clean.outputs.image_archive_name_stem }}.tar upload-artifact-retention:...

Thank you for posting it. I was just revisiting this yesterday and was getting a bit overwhelmed and distracted by all the flashy bits. I do want to put together...

As a workaround I added this function to my bash environment: ```bash awsume() { source "$(pyenv which awsume)" # Add the local time zone to AWSUME_EXPIRATION if it is missing...

I started seeing this issue on September 19th, 2023. I created [a repo to help diagnose the problem](https://github.com/felddy/npm-hang-test), or to detect when a fix is made upstream. It runs daily...

I like this idea, and have thought about doing something like this. The first step was to find an API or other data source that has all the FoundryVTT releases....

The last release of the container in the `10` series is [`10.303`](https://github.com/felddy/foundryvtt-docker/releases/tag/v10.303.0). If you want to use `10.312` you can follow the procedure here: - https://github.com/felddy/foundryvtt-docker/issues/868#issuecomment-1939130534 Use the `felddy/foundryvtt:release` container...

How are you "populating the Certificate and Key fields"? I suspect that you are not using the environment variables: `FOUNDRY_SSL_CERT`, and `FOUNDRY_SSL_KEY`, which are used by the [health check script](https://github.com/felddy/foundryvtt-docker/blob/develop/src/check_health.sh).

I'll take a look at this but my guess is that this is not a bug in the container implementation. Possibly related: - https://github.com/foundryvtt/foundryvtt/issues/7307

Agreed that this should be relatively straightforward to implement. I have a concern about how the tool stores its configuration in the `root` user's home directory. This could be problematic...