Skip to content

Backend container fails with missing entrypoint when built locally #440

@msinha569

Description

@msinha569

Description

When the backend service is built locally using:

build: ./surfsense_backend

the container fails to start and shows:

Image

exec /app/scripts/docker/entrypoint.sh: no such file or directory

However, when the backend runs directly from the prebuilt image (using only the image: tag and removing build:), everything works correctly.

image: ghcr.io/modsetter/surfsense_backend:latest

Steps to reproduce

Clone the repository.

In docker-compose.yml, configure the backend service as:

build: ./surfsense_backend
#image: ghcr.io/modsetter/surfsense_backend:latest

Run:

docker compose up -d

Observe container logs:

exec /app/scripts/docker/entrypoint.sh: no such file or directory

Remove the build: line and uncomment the image line -> run again.
→ Backend works as expected.

Expected behavior

The backend container should start successfully regardless of whether it is built locally or pulled from the registry.

Actual behavior

Locally built backend container exits immediately with error code 255 due to a missing or non-executable entrypoint script.

Possible cause

unknown

Environment

OS: Windows 10

Docker Desktop: latest

Compose version: v2.x

Backend directory: ./surfsense_backend

Error code: 255

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions