alshedivat/al-folio

Docker Image Slim Version is Broken

Open

#3,173 opened on May 22, 2025

View on GitHub
 (9 comments) (1 reaction) (0 assignees)HTML (15,603 stars) (12,991 forks)batch import
bughelp wanted

Description

Have you checked that your issue isn't already filed?

  • I read through FAQ and searched through the past issues, none of which addressed my issue.
  • Yes, I have checked that this issue isn't already filed.

Bug description

The slim version of docker image is broken

How to reproduce the bug

Run with docker compose -f docker-compose-slim.yml up and it would give:

Error messages and logs

2025-05-22 12:51:47 /usr/local/bundle/bin/bundle:25:in `load': cannot load such file -- /usr/local/bundle/gems/bundler-2.5.22/exe/bundle (LoadError)
2025-05-22 12:51:47     from /usr/local/bundle/bin/bundle:25:in `<main>'
2025-05-22 12:51:47 Entry point script running
2025-05-22 12:51:47 Gemfile.lock is tracked by git, keeping it intact

What operating system are you using?

Windows

Where are you seeing the problem on?

Running locally with Docker (docker compose)

More info

No response

Contributor guide

Tech stack
dockerruby
Domain
devopsbuild system
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
DockerRubyBundlerDocker Compose
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
55
Research direction
The bug is in the slim Docker image configuration. Start by examining the docker compose slim.yml file and the associated Dockerfile (likely Dockerfile slim) in the repository root. The error indicates bundler cannot load its own executable, suggesting a path issue during gem installation. Check if the Dockerfile uses a multi stage build or has a mismatch between Ruby and bundler versions. Also review recent commits that might have changed the Docker setup. Testing with a fresh build and comparing with the non slim version (docker compose.yml) could help isolate the problem.