[Bug]: Lock folders not being deleted after scan, preventing future updates without manual intervention #376

Closed
opened 2026-04-24 23:07:18 +02:00 by adam · 1 comment
Owner

Originally created by @ShaneK on GitHub (May 23, 2022).

Describe the issue

Running on docker on a Windows server, if I scan my library, the lock folders aren't deleted at the end. This has the consequence of preventing future updates to the library without going through and deleting the lock folders.

I've tried many things, like restarting the server, deleting the folders while the server was off and scanning again, deleting my config and meta folders (effectively resetting the instance) and none of it seems to fix the issue.

Steps to reproduce the issue

  1. Scan library
  2. Note that the lock folders weren't deleted
  3. Scan again
  4. Note that library isn't updated (if things were added/removed)

Audiobookshelf version

2.0.15

How are you running audiobookshelf?

Docker

Originally created by @ShaneK on GitHub (May 23, 2022). ### Describe the issue Running on docker on a Windows server, if I scan my library, the lock folders aren't deleted at the end. This has the consequence of preventing future updates to the library without going through and deleting the lock folders. I've tried many things, like restarting the server, deleting the folders while the server was off and scanning again, deleting my config and meta folders (effectively resetting the instance) and none of it seems to fix the issue. ### Steps to reproduce the issue 1. Scan library 2. Note that the lock folders weren't deleted 3. Scan again 4. Note that library isn't updated (if things were added/removed) ### Audiobookshelf version 2.0.15 ### How are you running audiobookshelf? Docker
adam added the bug label 2026-04-24 23:07:18 +02:00
adam closed this issue 2026-04-24 23:07:19 +02:00
Author
Owner

@ShaneK commented on GitHub (May 24, 2022):

So, I'm a little hesitant to say for certain, but it looks like I may have resolved this by adding privledged: true to the docker-compose.yml

No idea why this is necessary for me but apparently not others. It should be noted that I also cloned this repo locally and ran the app directly and had no issue at all, so it's definitely a docker permission problem.

@ShaneK commented on GitHub (May 24, 2022): So, I'm a little hesitant to say for certain, but it looks like I may have resolved this by adding `privledged: true` to the docker-compose.yml No idea why this is necessary for me but apparently not others. It should be noted that I also cloned this repo locally and ran the app directly and had no issue at all, so it's definitely a docker permission problem.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#376