2025-01-30, 05:52 PM
Can do - I'll have a look at the mount vs volumes options and see if there is anything in the Docker docs but it's odd how it works sometimes / manual but not automatically. The Docker docs do state:
I've been suffering with an eye issue (anti-bodies + my eyes = problems) but spent a bit of time going through the Github issue and found a bash script that regens the images - https://github.com/nagug/Jellyfin-Actor-Refresh-Script
Trying this reports 8317 images processed but still no luck for some pictures.
I did find this type of entry in the logs:
[2025-01-30 17:06:25.146 +00:00] [WRN] [83] Emby.Server.Implementations.Library.LibraryManager: Cannot fetch image from "https://image.tmdb.org/t/p//9aN6x2W7DlPAMX8MZxcqB1Hyf8v.jpg". Http status code: BadRequest
System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request).
at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
at MediaBrowser.Providers.Manager.ProviderManager.SaveImage(BaseItem item, String url, ImageType type, Nullable`1 imageIndex, CancellationToken cancellationToken)
at Emby.Server.Implementations.Library.LibraryManager.ConvertImageToLocal(BaseItem item, ItemImageInfo image, Int32 imageIndex, Boolean removeOnFailure)
at Emby.Server.Implementations.Library.LibraryManager.UpdateImagesAsync(BaseItem item, Boolean forceUpdate)
The URL is incorrect as it has two forward slashes next to each other. Removing this reports 'Image size not supported' as the API documentation says this should be the 'file size' - https://developer.themoviedb.org/docs/image-basics - putting 'original' or 'w500' in the URL does return a picture
https://image.tmdb.org/t/p/w500/9aN6x2W7...1Hyf8v.jpg
I'll continue going through the log once the eye is rested again and see if anything else pops up but its very very long :-(
I'll look at creating a new container as well - it will let me bring the server up to date and try the volume issue you mention.
Quote:In general, --mount is preferred. The main difference is that the --mount flag is more explicit and supports all the available optionsand the format I use in the compose is the mount version.
I've been suffering with an eye issue (anti-bodies + my eyes = problems) but spent a bit of time going through the Github issue and found a bash script that regens the images - https://github.com/nagug/Jellyfin-Actor-Refresh-Script
Trying this reports 8317 images processed but still no luck for some pictures.
I did find this type of entry in the logs:
[2025-01-30 17:06:25.146 +00:00] [WRN] [83] Emby.Server.Implementations.Library.LibraryManager: Cannot fetch image from "https://image.tmdb.org/t/p//9aN6x2W7DlPAMX8MZxcqB1Hyf8v.jpg". Http status code: BadRequest
System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request).
at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
at MediaBrowser.Providers.Manager.ProviderManager.SaveImage(BaseItem item, String url, ImageType type, Nullable`1 imageIndex, CancellationToken cancellationToken)
at Emby.Server.Implementations.Library.LibraryManager.ConvertImageToLocal(BaseItem item, ItemImageInfo image, Int32 imageIndex, Boolean removeOnFailure)
at Emby.Server.Implementations.Library.LibraryManager.UpdateImagesAsync(BaseItem item, Boolean forceUpdate)
The URL is incorrect as it has two forward slashes next to each other. Removing this reports 'Image size not supported' as the API documentation says this should be the 'file size' - https://developer.themoviedb.org/docs/image-basics - putting 'original' or 'w500' in the URL does return a picture
https://image.tmdb.org/t/p/w500/9aN6x2W7...1Hyf8v.jpg
I'll continue going through the log once the eye is rested again and see if anything else pops up but its very very long :-(
I'll look at creating a new container as well - it will let me bring the server up to date and try the volume issue you mention.