Skip to content

Fix build: bump Ruby to 3.4.12 and set RAILS_ASSETS_PRECOMPILE - #27

Closed
JeffreyBytes wants to merge 1 commit into
linuxserver:mainfrom
JeffreyBytes:ci/fixbuild
Closed

JeffreyBytes wants to merge 1 commit into
linuxserver:mainfrom
JeffreyBytes:ci/fixbuild

Conversation

@JeffreyBytes

Copy link
Copy Markdown

linuxserver.io


  • I have read the contributing guideline and understand that I have made the correct modifications
  • An LLM assisted me in writing the code or text for this PR
  • An LLM agent wrote the code or text for this PR

Description:

Two changes to both Dockerfiles, plus a changelog entry in readme-vars.yml.

  1. Bump the Ruby stage from ruby:3.4.9-alpine3.24 to ruby:3.4.12-alpine3.24. Upstream v0.154.0 moved .ruby-version to 3.4.12, and the Gemfile reads it (ruby file: ".ruby-version"), so bundle install currently fails with "Your Ruby version is 3.4.9, but your Gemfile specified 3.4.12".
  2. Set RAILS_ASSETS_PRECOMPILE=1 for rake assets:precompile. Since v0.151.0, config/initializers/cache_clearance.rb clears a Redis cache on boot unless that variable is set. Upstream's own docker/build.dockerfile sets it for precompile. Without it, precompile tries to reach Redis on localhost:6379 during the build and fails with Redis::CannotConnectError.

Benefits of this PR and context:

The image hasn't published since v0.150.0. Every build from v0.151.0 onward fails at asset precompile because of the Redis connection, and v0.154.x also fails earlier on the Ruby version mismatch (CI build 1030). With both changes, the current upstream release builds and runs.

How Has This Been Tested?

Tested on CachyOS (x86_64) with Docker.

Built v0.154.1 with these changes:

docker build --no-cache --pull --build-arg MANYFOLD_VERSION=v0.154.1 --build-arg VERSION=local-test --build-arg BUILD_DATE=... -t lscr.io/linuxserver/manyfold:test .

The build completed, including bundle install and assets:precompile.

Ran the image with SQLite (DATABASE_URL=sqlite3:/config/manyfold.sqlite3) and a Valkey 8 container for REDIS_URL. Init completed ([ls.io-init] done.), the web UI loaded on port 3214, and the container restarted cleanly against the existing /config.

I didn't build aarch64 locally. The changes are identical in both Dockerfiles and nothing is architecture-specific.

AI disclosure: I used Claude (Anthropic) to help trace the CI failures to these two causes and to draft this description. I made, built and tested the changes myself.

Source / References:

@github-actions

Copy link
Copy Markdown

Thanks for opening this pull request! Be sure to follow the pull request template!

@thespad

thespad commented Nov 15, 2026

Copy link
Copy Markdown
Member

Already addressed in #26

@thespad thespad closed this Nov 15, 2026
@LinuxServer-CI LinuxServer-CI moved this from PRs to Done in Issue & PR Tracker Nov 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

2 participants