Skip to content

build(docker): Switch app, Postgres, and Redis images to Alpine#99

Open
claudiocebpaz wants to merge 1 commit intonickjj:mainfrom
claudiocebpaz:pr/alpine-images
Open

build(docker): Switch app, Postgres, and Redis images to Alpine#99
claudiocebpaz wants to merge 1 commit intonickjj:mainfrom
claudiocebpaz:pr/alpine-images

Conversation

@claudiocebpaz
Copy link
Copy Markdown

Summary

  • Migrates Dockerfile build/runtime stages to Alpine-based Ruby images.
  • Replaces Debian package installation (apt) with Alpine equivalents (apk) while preserving the existing asset build flow.
  • Updates compose.yaml service images to Alpine variants for Postgres and Redis.

How to test

  • docker compose build
  • docker compose up
  • Verify web, postgres, and redis start correctly.
  • Run project checks/tests via the wrapper (./run ...).

Additional context

  • This Alpine-based setup has been running in production in my environment for an extended period.
  • Operationally, it has been stable, and resource consumption has been lower compared to the previous Debian-based configuration.

@nickjj
Copy link
Copy Markdown
Owner

nickjj commented Apr 3, 2026

Hi,

I appreciate the PR but I don't think switching to Alpine is the right fit for this project.

Can you provide exhaustive benchmarks on how you directly compared resource consumption between Debian and Alpine and Alpine has been much lower? Preferably separate CPU, memory, network and disk I/O stats at runtime along with the test projects you used to do this (if possible) and how it was measured.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants