Open sermelipharo opened 1 week ago
I think that I'm having this issue too. I was doing some testing and found that on each restart I had to delete the gem cache volume. Without deleting the gem cache volume I was getting errors like this constantly:
dawarich | /usr/local/lib/ruby/site_ruby/3.3.0/rubygems.rb:16:in `require_relative': cannot load such file -- /usr/local/lib/ruby/site_ruby/3.3.0/rubygems/compatibility (LoadError)
dawarich | from /usr/local/lib/ruby/site_ruby/3.3.0/rubygems.rb:16:in `<top (required)>'
dawarich | from <internal:gem_prelude>:2:in `require'
dawarich | from <internal:gem_prelude>:2:in `<internal:gem_prelude>'
dawarich | /usr/local/lib/ruby/site_ruby/3.3.0/rubygems.rb:16:in `require_relative': cannot load such file -- /usr/local/lib/ruby/site_ruby/3.3.0/rubygems/compatibility (LoadError)
dawarich | from /usr/local/lib/ruby/site_ruby/3.3.0/rubygems.rb:16:in `<top (required)>'
dawarich | from <internal:gem_prelude>:2:in `require'
dawarich | from <internal:gem_prelude>:2:in `<internal:gem_prelude>'
This doesn't seem to happen to me anymore. Was it just a one time glitch for our setups, or was it fixed, or is it still a possible issue?
@sermelipharo Are you still having this issue?
seems to be fixed
Describe the bug
After updating
dawarich_app
from version 0.15.3 to 0.15.4, the app container fails to start. No changes were made to the configuration, and downgrading back to 0.15.3 resolves the issue. The issue seems to be related to gem caching, and clearing the gem cache before the update might help.Version
Dawarich version: 0.15.4
To Reproduce
Steps to reproduce the behavior:
dawarich_app
container image to version 0.15.4.docker-compose up
to restart the services.dawarich_app
fails to start.Expected behavior
The
dawarich_app
container should start without issues after upgrading from 0.15.3 to 0.15.4.Screenshots
N/A.
Logs
Logs from
dawarich_app
container after the failed start:Additional context
Clearing the gem cache before the update (either manually or by deleting the
gem_cache
volume) resolves the issue, suggesting that the problem might be related to gem caching.