Newly published docker images for v1.9.1?

[marcoroth]

Hey friends, thanks for maintaining this awesome gem! ❤️

I just noticed that new docker images were published for v1.9.1 19 hours ago (which is the version released back in January):
https://github.com/rake-compiler/rake-compiler-dock/pkgs/container/rake-compiler-dock-image/versions

And as a result (at least I think so) I started to seeing failures in the Herb CI, without updating the gem or the Ruby version:
https://github.com/marcoroth/herb/actions/runs/16625692383/job/47041649259

Digest: sha256:1231e49cbe478478749928c69373c34644066d98cdeb21545125561977369ed7
Status: Downloaded newer image for ghcr.io/rake-compiler/rake-compiler-dock-image:1.9.1-mri-x86_64-linux-gnu
rbenv: version `3.4.1' is not installed (set by /home/runner/work/herb/herb/.ruby-version)
rake aborted!
Command failed with status (1): [docker run -v /home/runner/work/herb/herb:/home/runner/work/herb/herb -e UID\=1001 -e GID\=118 -e USER\=runner -e GROUP\=docker -e GEM_PRIVATE_KEY_PASSPHRASE -e SOURCE_DATE_EPOCH -e ftp_proxy -e http_proxy -e https_proxy -e RCD_HOST_RUBY_PLATFORM\=x86_64-linux -e RCD_HOST_RUBY_VERSION\=3.4.1 -e RCD_IMAGE\=ghcr.io/rake-compiler/rake-compiler-dock-image:1.9.1-mri-x86_64-linux-gnu -w /home/runner/work/herb/herb --rm -i ghcr.io/rake-compiler/rake-compiler-dock-image:1.9.1-mri-x86_64-linux-gnu runas sigfw bash -c bundle\ --local\ \&\&\ rake\ native:x86_64-linux-gnu\ gem\ RUBY_CC_VERSION\=\'3.4.1:3.3.7:3.2.6:3.1.6:3.0.7\']
/home/runner/work/herb/herb/vendor/bundle/ruby/3.4.0/gems/rake-compiler-dock-1.9.1/lib/rake_compiler_dock/starter.rb:90:in 'block in RakeCompilerDock::Starter.exec'
/home/runner/work/herb/herb/vendor/bundle/ruby/3.4.0/gems/rake-compiler-dock-1.9.1/lib/rake_compiler_dock/starter.rb:44:in 'Array#each'
/home/runner/work/herb/herb/vendor/bundle/ruby/3.4.0/gems/rake-compiler-dock-1.9.1/lib/rake_compiler_dock/starter.rb:44:in 'RakeCompilerDock::Starter.exec'
/home/runner/work/herb/herb/vendor/bundle/ruby/3.4.0/gems/rake-compiler-dock-1.9.1/lib/rake_compiler_dock/starter.rb:14:in 'RakeCompilerDock::Starter.sh'
/home/runner/work/herb/herb/vendor/bundle/ruby/3.4.0/gems/rake-compiler-dock-1.9.1/lib/rake_compiler_dock.rb:47:in 'RakeCompilerDock.sh'
/home/runner/work/herb/herb/Rakefile:97:in 'block (3 levels) in <top (required)>'
/home/runner/work/herb/herb/vendor/bundle/ruby/3.4.0/gems/rake-13.3.0/exe/rake:27:in '<top (required)>'
/opt/hostedtoolcache/Ruby/3.4.1/x64/bin/bundle:25:in 'Kernel#load'
/opt/hostedtoolcache/Ruby/3.4.1/x64/bin/bundle:25:in '<main>'
Tasks: TOP => gem:x86_64-linux-gnu
(See full trace by running task with --trace)
Error: Process completed with exit code 1.

However, bumping the Ruby Version to 3.4.5 fixes the issue.

It seems like this pull request (#156) which is now on main was published on the old version. Though this is a bit surprising since the docker image was (re?)published using the old version number from January.

Or am I missing something?

[flavorjones]

I'm trying to figure out what happened here while I'm on vacation. the 1.9.1 images have indeed been updated.

• The "publish" workflow was run, but that should only update snapshots.
• It doesn't look like the "release" workflow was run.

@larskanis did you by any chance push those images from your development environment? If you didn't, then something's wrong with the "publish" workflow and it's pushing release tags.

[flavorjones]

@larskanis it looks like the "publish" workflow is pushing release tags:

https://github.com/rake-compiler/rake-compiler-dock/actions/runs/16613136043/job/47000410308#step:8:590

[flavorjones]

I'm re-running the "release" pipeline for v1.9.1 which should clobber the current images with the previous 1.9.1 images.

https://github.com/rake-compiler/rake-compiler-dock/actions/runs/16671386191

[larskanis]

Haha, I just checked this issue on my end. The first tag snapshot is defined in the GHA workflow and the second tag 1.9.1 here.

[larskanis]

I accidentally pushed the 1.9.1 images, because the new build process adds the tags and pushes in the same command (necessary for multi-platform images), while the old process tagged equally, but pushed only the snapshot tag in a second command.

[flavorjones]

@marcoroth The v1.9.1 images should be back in usable shape now (see comment above about re-pushing the tag). Let me know if it works for you?