Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with Foundry docker container starting sometimes #1143

Open
1 task done
etriebe opened this issue Jan 24, 2025 · 2 comments
Open
1 task done

Issue with Foundry docker container starting sometimes #1143

etriebe opened this issue Jan 24, 2025 · 2 comments

Comments

@etriebe
Copy link

etriebe commented Jan 24, 2025

Bug description

Issue with starting the docker container.

Steps to reproduce

  1. Start the container

Expected behavior

No error

Container metadata

com.foundryvtt.version = "12.331"
org.opencontainers.image.authors = "[email protected]"
org.opencontainers.image.created = "2024-08-16T01:48:32.610Z"
org.opencontainers.image.description = "An easy-to-deploy Dockerized Foundry Virtual Tabletop server."
org.opencontainers.image.licenses = "MIT"
org.opencontainers.image.revision = "61a1ac11d7bd298b93fa6cebb102158ddb1d020e"
org.opencontainers.image.source = "https://github.com/felddy/foundryvtt-docker"
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 = "12.331.0"

Relevant log output

FoundryVTT | 2025-01-24 00:35:23 | [info] Foundry Virtual Tabletop - Version 12 Build 331
FoundryVTT | 2025-01-24 00:35:23 | [info] User Data Directory - "/data"
FoundryVTT | 2025-01-24 00:35:23 | [error] A fatal error occurred while trying to start the Foundry Virtual Tabletop server: Foundry VTT cannot start in this directory which is already locked by another process.
Error: A fatal error occurred while trying to start the Foundry Virtual Tabletop server: Foundry VTT cannot start in this directory which is already locked by another process.
    at _acquireLockFile (file:///home/foundry/resources/app/dist/init.mjs:1:5233)
    at async _initializeCriticalFunctions (file:///home/foundry/resources/app/dist/init.mjs:1:2861)
    at async Module.initialize (file:///home/foundry/resources/app/dist/init.mjs:1:1788)

Code of Conduct

  • I agree to follow this project's Code of Conduct
@felddy
Copy link
Owner

felddy commented Jan 24, 2025

Please run the container with CONTAINER_VERBOSE set to true ,and update the log output in the issue.

This is probably not an issue with the container itself. Here are some other related reports of similar issue that may help you:
https://github.com/search?q=repo%3Afelddy%2Ffoundryvtt-docker+already+locked+by+another+process

Specifically:

@etriebe
Copy link
Author

etriebe commented Jan 28, 2025

I turned on CONTAINER_VERBOSE = true and there aren't any new logs that make this easier to diagnose. In addition, this seems to happen when the

FoundryVTT | 2025-01-28 00:16:54 | [info] User Data Directory - "/data"
FoundryVTT | 2025-01-28 00:16:55 | [error] A fatal error occurred while trying to start the Foundry Virtual Tabletop server: Foundry VTT cannot start in this directory which is already locked by another process.
Error: A fatal error occurred while trying to start the Foundry Virtual Tabletop server: Foundry VTT cannot start in this directory which is already locked by another process.
    at _acquireLockFile (file:///home/foundry/resources/app/dist/init.mjs:1:5233)
    at async _initializeCriticalFunctions (file:///home/foundry/resources/app/dist/init.mjs:1:2861)
    at async Module.initialize (file:///home/foundry/resources/app/dist/init.mjs:1:1788)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants