mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
[Bug]: MODULE_NOT_FOUND error in Docker, crashing on startup #2783
Open
opened 2026-04-25 00:10:35 +02:00 by adam
·
26 comments
No Branch/Tag Specified
master
book_tags_genres_dedupe
episode_download_fallback
Issue-4540-SortBy-StartedDate-and-FinishedDate
episode_meta_tagging
fix_authorize_race_condition
redirect_transcode_requests
progress_updated_sort
fix_ereader_socket_event
fix_change_empty_root_password
fix_podcast_session_track_index
fix_set_token
session_modal_user
localize_durations
fix_oidc_create_user
jwt_auth_refactor
fix_scanner_deleting_single_file_books
fix_mediaprogress_updatedat_2
experimental_next_client
podcast_episode_duration
episode-timestamps-clickable
book_author_secondary_sort_title
podcast_useragents
pathexists_user_access
fix_pathexists_join
book_author_secondary_sort
clean_duplicate_mediaprogress
sanitize_html_description
trix_prevent_attachments
check_path_api_fix
fix_mediaprogress_updatedat
increase_express_json_limit
fix_dockerfile_nunicode
search_episodes
audiobook_tools_update
episode_secondary_sorts
hls_stream_url_update
new_session_track_endpoint
audiobook_tools_enhancements
watcher_rescans_update
player_track_tooltip
fix_exclude_prefixes_crash
socket_item_events
fix_podcast_episode_scanner_promise
new_stats_controller
count_cache_for_userpermissions
parsing-opf-v3
validate_migration_files
fix-quick-match-all-crash
fix-chapter-end-sleep-timer
stringify_sequelize_query
remove-col-ambiguity
fix_next_prev_edit_description
details_trim_whitespace
fix_content_url_basepath
fix_logger_fatal
progress_bar_visibility
batch-edit-populate-map-details
feed_generator_updates
bookmark-modal-updates
migrate-library-item-in-scanner
migrate-new-library-items
migrate-podcasts-new-library-item-2
migrate-podcasts-new-library-item
fix-remove-episode-from-playlist
playback-session-use-new-library-item
refactor-library-item
fix-heatmap-caption
feed-episodes-upsert
share-media-player-media-session-api
remove-old-playlist
remove_old_collection_object
plugin-implementation-demo
feed_migration
refactor-feeds-from-item
fix_remove_authors_no_books
v2.17.3-fk-constraints-migration
migrations-first-upgrade
sqlite_2
feature/nuxt-target-server
waveform
sqlite
playlists
video
v2.35.1
v2.35.0
v2.34.0
v2.33.2
v2.33.1
v2.33.0
v2.32.1
v2.32.0
v2.31.0
v2.30.0
v2.29.0
v2.28.0
v2.27.0
v2.26.3
v2.26.2
v2.26.1
v2.26.0
v2.25.1
v2.25.0
v2.24.0
v2.23.0
v2.22.0
v2.21.0
v2.20.0
v2.19.5
v2.19.4
v2.19.3
v2.19.2
v2.19.1
v2.19.0
v2.18.1
v2.18.0
v2.17.7
v2.17.6
v2.17.5
v2.17.4
v2.17.3
v2.17.2
v2.17.1
v2.17.0
v2.16.2
v2.16.1
v2.16.0
v2.15.1
v2.15.0
v2.14.0
v2.13.4
v2.13.3
v2.13.2
v2.13.1
v2.13.0
v2.12.3
v2.12.2
v2.12.1
v2.12.0
v2.11.0
v2.10.1
v2.10.0
v2.9.0
v2.8.1
v2.8.0
v2.7.2
v2.7.1
v2.7.0
v2.6.0
v2.5.0
v2.4.4
v2.4.3
v2.4.2
v2.4.1
v2.4.0
v2.3.5
v2.3.4
v2.3.3
v2.3.2
v2.3.1
v2.3.0
v2.2.23
v2.2.22
v2.2.21
v2.2.20
v2.2.19
v2.2.18
v2.2.17
v2.2.16
v2.2.15
v2.2.14
v2.2.13
v2.2.12
v2.2.11
v2.2.10
v2.2.9
v2.2.8
v2.2.7
v2.2.6
v2.2.5
v2.2.4
v2.2.3
v2.2.2
v2.2.1
v2.2.0
v2.1.5
v2.1.4
v2.1.3
v2.1.2
v2.1.1
v2.1.0
v2.0.24
v2.0.23
v2.0.22
v2.0.21
v2.0.20
v2.0.19
v2.0.18
v2.0.17
v2.0.16
v2.0.15
v2.0.14
v2.0.13
v2.0.12
v2.0.11
v2.0.10
v2.0.9
v2.0.8
v2.0.7
v2.0.6
v2.0.5
v2.0.4
v2.0.3
v2.0.2
v2.0.1
v1.7.2
v1.7.1
v1.7.0
v1.6.0
v1.5.5
v1.5.0
v1.4.11
v1.4.9
v1.4.7
v1.4.6
v1.4.4
v1.4.2
v1.4.0
v1.4.1
v1.3.4
v1.3.3
v1.3.1
v1.2.8
v1.2.6
v1.2.5
v1.2.4
v1.2.1
v1.1.15
v1.1.14
v1.1.13
v1.1.12
v1.1.11
v1.1.10
v1.1.9
v1.1.8
v1.0.0
0.9.61-beta.0
0.9.61-beta
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
Mirrored from GitHub Pull Request
No Label
bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
adam (Adam Melkus)
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/audiobookshelf#2783
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dima-ser on GitHub (May 18, 2025).
What happened?
Updated to latest docker image. Container crashing after startup. See logs below
What did you expect to happen?
I expected it to not crash
Steps to reproduce the issue
Audiobookshelf version
2.23.0
How are you running audiobookshelf?
Docker
What OS is your Audiobookshelf server hosted from?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
None
Logs
Additional Notes
Running on Synology
@DieselTech commented on GitHub (May 18, 2025):
Duplicate of https://github.com/advplyr/audiobookshelf/issues/4292
Check that thread for answers. tl;dr - this is a synology issue.
@dima-ser commented on GitHub (May 18, 2025):
Thanks, I did a "Clean" on the project, rebuilt it and now it works. Not sure why.
@DieselTech commented on GitHub (May 18, 2025):
It works because synology does really weird stuff on their own that isn't part of docker. They were caching environment variables and other parts of the image that shouldn't be cached. Forcing it to create a new container gets around that problem.
@Dinth commented on GitHub (May 18, 2025):
Im experiencing the same issue on Debian running on normal baremetal server, defo nothing to do with Synology.
Here is my docker-compose:
And the log repeadly shows:
it was working fine until an update a few days ago (maybe up to two weeks ago). Completely destroying the stack and redeploying the compose file still doesnt work
@nichwall commented on GitHub (May 18, 2025):
Make sure you have fully removed the existing container and image, then pull the image again. It affects more than just Synology, but Synology has been the worst offender.
@Dinth commented on GitHub (May 18, 2025):
I have destroyed the stack, removed all the images:
and redeployed compose file, but still doesnt help. I have also tried adding ghcr.io/ prefix to the container address
@pax0707 commented on GitHub (May 18, 2025):
Just had this happen to me.
Recreating the stack fixed it.
@nichwall commented on GitHub (May 19, 2025):
What about
docker ps -a? Those are just the images@Dinth commented on GitHub (May 19, 2025):
same thing, ive been deleting container on each attempt
docker inspect:
@nichwall commented on GitHub (May 19, 2025):
I'm not seeing any of those SHA for the last few releases at https://github.com/advplyr/audiobookshelf/pkgs/container/audiobookshelf (but I could be missing it, I only checked the last few releases).
@Dinth commented on GitHub (May 19, 2025):
hmmm should the image sha in docker inspect match the image sha on docker hub? Now ive tried
image: ghcr.io/advplyr/audiobookshelf@sha256:2d8bee3e87e860d67e11e13b5c42d97cb1fe071de53dea5502b3a9292e75e024in docker compose, docker inspect still shows
"Image": "sha256:9958782bff325541baaa94097e03cc59ac3c2530b7af349ee23e08c4448ccd5b",@Dinth commented on GitHub (May 19, 2025):
hmmm
@nichwall commented on GitHub (May 19, 2025):
What happens if you change your compose from
:latestto:2.23.0?@Dinth commented on GitHub (May 19, 2025):
My problem resolved, i had working_dir set in my compose file and it looks like it has changed recently, the other thread pointed me towards this.
@nichwall commented on GitHub (May 19, 2025):
Thanks for confirming. Out of curiosity, why did you have
working_dirset? Did you do that yourself or see that in a guide?@Dinth commented on GitHub (May 19, 2025):
Ive migrated from docker standalone to docker compose with a help of docker-autocompose 🤭
@nichwall commented on GitHub (May 19, 2025):
Thanks, that is good to know that it is from a specific tool and something for us to look out for when other people are reporting upgrade issues.
@HikariNoKitsune commented on GitHub (May 20, 2025):
This was my issue. For reference, when I made it, I just used normal docker compose, but it set the working directory as "/" (no quotes) according to what portainer is showing me. Apparently in this latest update, they changed this... Since the above quote didn't really specify on 'what to do', I just removed the "/" and left it blank, and that seems to have worked...
@nichwall commented on GitHub (May 20, 2025):
Yeah, unless you are specifically doing something to try and edit stuff within the container or really know what you are doing, you should not set
work_dirin a compose.@Seventy-9DegreesNorth commented on GitHub (May 23, 2025):
I had the same issue. Using Cosmos Server on a Ubuntu Server 24 and the composes get modified by Cosmos when it runs them. Whatever happened with a recent upgrade to Audiobookshelf my port mapping statements wouldn't "stick" in the compose and the container wouldn't stay started. To be clear on the solution, as above, I removed the "work_dir" entry completely in the compose and restarted the container. It restarted but was unaccessible because the ports. Then I could update the port mapping and it stuck. So, problem resolved. Thank you for posting these solutions. Appears to be resolved, but the updates going forward should look for this issue.
@nichwall commented on GitHub (May 23, 2025):
The
work_dirandportbeing modified by other tools (such as Cosmos) is outside the control of the container (in this case Audiobookshelf). If your container manager/compose wrapper is caching previous versions or setting things incorrectly, you will need to make sure older versions of the container and image are removed when updating.@DieselTech commented on GitHub (May 23, 2025):
You should file a bug report with Cosmos for modifying compose files that they shouldn't be touching. As nichwall stated, this is outside of ABS's control.
@Seventy-9DegreesNorth commented on GitHub (May 23, 2025):
It's a fair point - I didn't mean to imply blame -- from the user's perspective it's hard to know where the problem arises, since there are always multiple systems. It appeared from the thread that ABS updates triggered a change that people were having problems with, and that the solution proposed worked. I honestly can't understand why Cosmos feels it has to modify the composes -- it's not ABS' issue for sure -- just pointing it out in the event there were any other ABS/Cosmos users and if the issue WAS with the update. Apologies.
@HikariNoKitsune commented on GitHub (May 23, 2025):
The thing for me, was that I didn't set a work_dir in compose. at least its not in the compose file i have in portainer. so idk when it got switched to that. just a curiosity i guess
@eskiiom commented on GitHub (Jul 7, 2025):
Thank you very much. I confirm it fixed the issue for me too.
I was stuck on image 2.21.0 and couldn't upgradE. Tried re-pulling the image many times, clearing /config and /metadata
It was just that the 2.21 image pushed "/" as a working dir where all versions after need "/app"
Not knowing that I had to re-build AND remove the working dir field to have the latest image pushing /app at the rebuild.
I learned how to fix this today. Thank you Internet 🥇
@ftgwgames commented on GitHub (Aug 17, 2025):
Holy shit, THANK YOU! This fixed the issue. Been dealing with it for months...