You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When generating active record credential with "docker run --rm -it --entrypoint /bin/bash lscr.io/linuxserver/mastodon:glitch generate-active-record" it fails (on latest glitch arm64 branch)
Expected Behavior
Generation of ACTIVE_RECORD_ENCRYPTION_DETERMINISTIC_KEY, ACTIVE_RECORD_ENCRYPTION_KEY_DERIVATION_SALT, & ACTIVE_RECORD_ENCRYPTION_PRIMARY_KEY
Steps To Reproduce
On Ubuntu 22.04, with docker 26.0.2, run "docker run --rm -it --entrypoint /bin/bash lscr.io/linuxserver/mastodon:glitch generate-active-record"
Environment
- OS: Ubuntu 22.04
- How docker service was installed: distro's package manager
- Docker : 26.0.2
CPU architecture
arm64
Docker creation
docker run --rm -it --entrypoint /bin/bash lscr.io/linuxserver/mastodon:glitch generate-active-record
Container logs
rake aborted!
LoadError: cannot load such file -- nokogiri/nokogiri (LoadError)
/app/www/vendor/bundle/ruby/3.3.0/gems/bootsnap-1.18.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:27:in `require'/app/www/vendor/bundle/ruby/3.3.0/gems/nokogiri-1.16.6-aarch64-linux/lib/nokogiri/extension.rb:31:in `rescue in <main>'/app/www/vendor/bundle/ruby/3.3.0/gems/nokogiri-1.16.6-aarch64-linux/lib/nokogiri/extension.rb:4:in `<main>'/app/www/vendor/bundle/ruby/3.3.0/gems/nokogiri-1.16.6-aarch64-linux/lib/nokogiri.rb:8:in `require_relative'
/app/www/vendor/bundle/ruby/3.3.0/gems/nokogiri-1.16.6-aarch64-linux/lib/nokogiri.rb:8:in `<main>'/app/www/vendor/bundle/ruby/3.3.0/gems/bootsnap-1.18.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'/app/www/vendor/bundle/ruby/3.3.0/gems/ruby-saml-1.16.0/lib/onelogin/ruby-saml/saml_message.rb:4:in `<main>'/app/www/vendor/bundle/ruby/3.3.0/gems/bootsnap-1.18.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
/app/www/vendor/bundle/ruby/3.3.0/gems/ruby-saml-1.16.0/lib/onelogin/ruby-saml.rb:2:in `<main>'/app/www/vendor/bundle/ruby/3.3.0/gems/bootsnap-1.18.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'/app/www/vendor/bundle/ruby/3.3.0/gems/ruby-saml-1.16.0/lib/ruby-saml.rb:1:in `<main>'/app/www/vendor/bundle/ruby/3.3.0/gems/bootsnap-1.18.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
/app/www/vendor/bundle/ruby/3.3.0/gems/omniauth-saml-2.1.0/lib/omniauth/strategies/saml.rb:2:in `<main>'/app/www/vendor/bundle/ruby/3.3.0/gems/bootsnap-1.18.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'/app/www/vendor/bundle/ruby/3.3.0/gems/omniauth-saml-2.1.0/lib/omniauth-saml.rb:1:in `<main>'<internal:/usr/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in `require'<internal:/usr/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in `require'/app/www/config/application.rb:23:in `<main>'/app/www/vendor/bundle/ruby/3.3.0/gems/bootsnap-1.18.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'/app/www/Rakefile:6:in `<main>'
Caused by:
LoadError: Error loading shared library ld-linux-aarch64.so.1: No such file or directory (needed by /app/www/vendor/bundle/ruby/3.3.0/gems/nokogiri-1.16.6-aarch64-linux/lib/nokogiri/3.3/nokogiri.so) - /app/www/vendor/bundle/ruby/3.3.0/gems/nokogiri-1.16.6-aarch64-linux/lib/nokogiri/3.3/nokogiri.so (LoadError)
/app/www/vendor/bundle/ruby/3.3.0/gems/nokogiri-1.16.6-aarch64-linux/lib/nokogiri/extension.rb:7:in `require_relative'/app/www/vendor/bundle/ruby/3.3.0/gems/nokogiri-1.16.6-aarch64-linux/lib/nokogiri/extension.rb:7:in `<main>'/app/www/vendor/bundle/ruby/3.3.0/gems/nokogiri-1.16.6-aarch64-linux/lib/nokogiri.rb:8:in `require_relative'/app/www/vendor/bundle/ruby/3.3.0/gems/nokogiri-1.16.6-aarch64-linux/lib/nokogiri.rb:8:in `<main>'
/app/www/vendor/bundle/ruby/3.3.0/gems/bootsnap-1.18.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'/app/www/vendor/bundle/ruby/3.3.0/gems/ruby-saml-1.16.0/lib/onelogin/ruby-saml/saml_message.rb:4:in `<main>'/app/www/vendor/bundle/ruby/3.3.0/gems/bootsnap-1.18.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'/app/www/vendor/bundle/ruby/3.3.0/gems/ruby-saml-1.16.0/lib/onelogin/ruby-saml.rb:2:in `<main>'
/app/www/vendor/bundle/ruby/3.3.0/gems/bootsnap-1.18.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'/app/www/vendor/bundle/ruby/3.3.0/gems/ruby-saml-1.16.0/lib/ruby-saml.rb:1:in `<main>'/app/www/vendor/bundle/ruby/3.3.0/gems/bootsnap-1.18.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'/app/www/vendor/bundle/ruby/3.3.0/gems/omniauth-saml-2.1.0/lib/omniauth/strategies/saml.rb:2:in `<main>'
/app/www/vendor/bundle/ruby/3.3.0/gems/bootsnap-1.18.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'/app/www/vendor/bundle/ruby/3.3.0/gems/omniauth-saml-2.1.0/lib/omniauth-saml.rb:1:in `<main>'<internal:/usr/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in `require'<internal:/usr/lib/ruby/3.3.0/rubygems/core_ext/kernel_require.rb>:37:in `require'
/app/www/config/application.rb:23:in `<main>'/app/www/vendor/bundle/ruby/3.3.0/gems/bootsnap-1.18.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'/app/www/Rakefile:6:in `<main>'(See full trace by running task with --trace)
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current Behavior
When generating active record credential with "docker run --rm -it --entrypoint /bin/bash lscr.io/linuxserver/mastodon:glitch generate-active-record" it fails (on latest glitch arm64 branch)
Expected Behavior
Generation of ACTIVE_RECORD_ENCRYPTION_DETERMINISTIC_KEY, ACTIVE_RECORD_ENCRYPTION_KEY_DERIVATION_SALT, & ACTIVE_RECORD_ENCRYPTION_PRIMARY_KEY
Steps To Reproduce
On Ubuntu 22.04, with docker 26.0.2, run "docker run --rm -it --entrypoint /bin/bash lscr.io/linuxserver/mastodon:glitch generate-active-record"
Environment
CPU architecture
arm64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: