You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FoundryVTT | 2025-01-24 00:35:23 | [info] Foundry Virtual Tabletop - Version 12 Build 331FoundryVTT | 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
The text was updated successfully, but these errors were encountered:
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)
Bug description
Issue with starting the docker container.
Steps to reproduce
Expected behavior
No error
Container metadata
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: