Metadata location mismatch

[thostr 12]

Hi I'm not sure where my issues lie. So I will try here.

I have recently reinstalled Emby v. 4.8.10.0 in docker and my metadata management does not work as expected
In my docker-compose I specify the volume to be read only, and in library I untick "save in media folder", but it stil populates in the media folders.

And when I try to remove images from within Emby it correctly states its a Read Only file system. But I don't understand why Emby can place the files there in the first place?
I have even tried to delete all images and refresh metadata search, but the images still populate in media folders.

I have attached the logs as well with a recent metadata refresh

 

embyserver.txt

[Happy2Play 9780]

Not sure as all I see is a refresh unable to delete existing metadata/images.

/Items/13591/Refresh?Recursive=true&ImageRefreshMode=FullRefresh&MetadataRefreshMode=FullRefresh&ReplaceAllImages=true&ReplaceAllMetadata=true

Can't say when the images/nfo were written with media though.  Pretty sure you would need to enable debug logging also to see the saving dialog.

[thostr 12]

I have deleted images from library and refreshed it agiain.

The log throws error but the files are clearly placed in media folder again.

I have attached new logs

embyserver.txt

[Happy2Play 9780]

10 minutes ago, thostr said:

I have deleted images from library and refreshed it agiain.

The log throws error but the files are clearly placed in media folder again.
 

Don't follow as the error images are from 2023, what images did you remove? 

But yes I see that Season images which are not erroring but have new dates but I don't see them in the log.  Still probably need to enable DEBUG logging.

[Neminem 1518]

Can you test emby's official docker image.

emby/embyserver:latest

Instead of 3rd party compiled, even though they do a really good job.

[thostr 12]

I found the root case and it's not Emby related.

I've had another service that added the files so it all makes sense now.

My bad...