fix: replace bash -c with sh -c for Alpine compatibility (#22)

[NeritonDias]

Summary

The Docker images for evo-auth and evo-crm services are built on Alpine Linux (ruby:3.4.4-alpine3.21), which does not ship with bash. Using bash -c "..." in container commands fails at runtime with:

docker/entrypoints/rails.sh: exec: line 34: bash: not found
exit code 127

The rails.sh entrypoint ends with exec "$@", which tries to execute the command passed via docker-compose command:. When that command starts with bash, the exec fails because bash is not installed in the Alpine image.

All affected commands are simple && chains fully compatible with POSIX sh, so the fix is a straight swap of bash -c for sh -c.

Files Changed

File	Changes
docker-compose.yml	evo-auth, evo-auth-sidekiq commands
docker-compose.prod-test.yaml	evo_auth, evo_auth_sidekiq, evo_crm commands
docker-compose.swarm.yaml	evo_auth command
setup.sh	db seed commands for evo-auth and evo-crm
Makefile	seed-auth and seed-crm targets

Root Cause

1. Dockerfile uses FROM ruby:3.4.4-alpine3.21 — Alpine ships /bin/sh (BusyBox), not /bin/bash
2. docker-compose files pass bash -c "..." as the container command
3. docker/entrypoints/rails.sh line 34 runs exec "$@" which expands to exec bash -c "..."
4. bash binary doesn't exist in the container → exit code 127

Fixes

Closes #22

Test Plan

• make setup completes successfully without bash: not found errors
• make seed-auth runs and seeds the Auth service
• make seed-crm runs and seeds the CRM service
• docker compose up starts evo-auth and evo-auth-sidekiq correctly
• docker compose -f docker-compose.prod-test.yaml up still works
• All commands execute identically under sh (all are POSIX-compatible &&/||/; chains)

Summary by Sourcery

Replace bash-based container commands with POSIX sh for compatibility with Alpine-based images.

Bug Fixes:

• Ensure evo-auth and evo-crm containers start correctly on Alpine images by using sh instead of bash in docker-compose commands.
• Fix seeding commands for Auth and CRM services in setup script and Makefile to run under sh in Alpine containers.

Enhancements:

• Align Docker Compose and helper scripts to use POSIX-compliant shell commands across environments.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Replaces all uses of bash -c with sh -c in Docker Compose definitions, setup scripts, and Make targets to ensure compatibility with Alpine-based Ruby images that only provide /bin/sh while keeping the executed Rails and Sidekiq commands unchanged.

Sequence diagram for container startup before and after replacing bash with sh

sequenceDiagram
    actor Dev
    participant Makefile as Makefile_target
    participant Docker as docker_compose
    participant Container as Rails_container
    participant Entrypoint as rails_sh_entrypoint
    participant Shell as shell

    Dev->>Makefile: run seed-auth / docker compose up
    Makefile->>Docker: docker compose run evo-auth cmd
    note over Docker: command: bash -c "bundle exec rails ..." (before)
    Docker->>Container: start container with CMD
    Container->>Entrypoint: run rails.sh
    Entrypoint->>Entrypoint: exec "$@"
    Entrypoint->>Shell: exec bash -c "bundle exec rails ..."
    Shell-->>Entrypoint: bash not found (exit 127)
    Entrypoint-->>Container: process exits
    Container-->>Docker: container stops with error

    Dev->>Makefile: run seed-auth / docker compose up (after)
    Makefile->>Docker: docker compose run evo-auth cmd
    note over Docker: command: sh -c "bundle exec rails ..." (after)
    Docker->>Container: start container with CMD
    Container->>Entrypoint: run rails.sh
    Entrypoint->>Entrypoint: exec "$@"
    Entrypoint->>Shell: exec sh -c "bundle exec rails ..."
    Shell->>Shell: run bundle exec rails db:prepare
    Shell->>Shell: run bundle exec rails db:seed or rails s / sidekiq
    Shell-->>Entrypoint: commands complete
    Entrypoint-->>Container: process stays running (services healthy)

Loading

Flow diagram for seeding services using sh -c via Makefile and setup script

flowchart LR
    Dev["Developer runs make setup / make seed-auth / make seed-crm"] --> Makefile["Makefile targets seed-auth and seed-crm"]
    Makefile -->|docker compose run --rm evo-auth sh -c 'bundle exec rails db:prepare && bundle exec rails db:seed'| DockerAuth["docker compose run evo-auth"]
    Makefile -->|docker compose run --rm evo-crm sh -c 'bundle exec rails db:prepare && bundle exec rails db:seed'| DockerCrm["docker compose run evo-crm"]

    Dev --> SetupSh["setup.sh script"]
    SetupSh -->|docker compose run --rm evo-auth sh -c 'bundle exec rails db:prepare && bundle exec rails db:seed'| DockerAuth
    SetupSh -->|docker compose run --rm evo-crm sh -c 'bundle exec rails db:prepare && bundle exec rails db:seed'| DockerCrm

    DockerAuth --> EntrypointAuth["evo-auth rails.sh entrypoint"]
    DockerCrm --> EntrypointCrm["evo-crm rails.sh entrypoint"]

    EntrypointAuth --> ExecAuth["exec sh -c ..."]
    EntrypointCrm --> ExecCrm["exec sh -c ..."]

    ExecAuth --> AuthPrepare["bundle exec rails db:prepare"]
    AuthPrepare --> AuthSeed["bundle exec rails db:seed"]
    AuthSeed --> AuthDone["Auth database seeded"]

    ExecCrm --> CrmPrepare["bundle exec rails db:prepare"]
    CrmPrepare --> CrmSeed["bundle exec rails db:seed"]
    CrmSeed --> CrmDone["CRM database seeded"]

Loading

File-Level Changes

Change	Details	Files
Switch container start commands from bash to POSIX sh for Alpine-based evo_auth/evo_crm images.	Update evo_auth service command to use sh -c for running bundle install, DB prepare, and Rails server. Update evo_auth_sidekiq service command to use sh -c for running bundle install and Sidekiq worker. Update evo_crm service command to use sh -c for running DB prepare and Rails server. Ensure chained Rails commands remain POSIX-compliant (&&, `
Align local seeding workflows with Alpine images by using sh in docker-compose run invocations.	Change Auth service seeding command to run via sh -c instead of bash -c. Change CRM service seeding command to run via sh -c instead of bash -c. Keep all Rails db:prepare and db:seed command chains identical aside from the shell used.	Makefile setup.sh

Possibly linked issues

• #N/A: Yes. The PR replaces bash -c with sh -c in make/setup seeding and compose commands fixing the reported bash-not-found error.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}