chapel-lang/chapel

[Bug]: Dockerfile does not include a CMD command

Open

#25,955 opened on Sep 17, 2024

View on GitHub
 (1 comment) (1 reaction) (1 assignee)Chapel (446 forks)auto 404
area: BTReasy / straightforwardgood first issuetype: Bug

Repository metrics

Stars
 (2,010 stars)
PR merge metrics
 (PR metrics pending)

Description

Summary of Problem

Our Dockerfile for Chapel does not include a CMD nor an ENTRYPOINT. From the Docker docs: https://docs.docker.com/reference/dockerfile/#understand-how-cmd-and-entrypoint-interact

Dockerfile should specify at least one of CMD or ENTRYPOINT commands. No CMD and no ENTRYPOINT is an error, and is not allowed.

How does our Docker image build successfully then? We inherit the default CMD command from the debian 11 image which we use as our base.

We should not rely on this behavior from debian, and instead should add a line to our Dockerfile that says

CMD ["/bin/bash"]

Contributor guide

Research direction
Add a CMD instruction to the Dockerfile to explicitly specify the default command.
Tech stack
docker
Domain
devops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
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
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90