Allow overriding the default naming scheme for containers and other entities
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38.2k
- Forks
- 5.8k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 55
Description
Description
I would love to have the option to declare a custom default naming scheme for every service in my docker-compose.yml file.
Since I don't like having the project/directory name prefix contained in my services, right now I have to specify the container_name element for every service I create like this:
services:
foo:
image: ubuntu
container_name: foo
bar:
image: nginx
container_name: bar
This could be accomplished by allowing the user to specify a top level element like this or something similar to it:
naming_scheme: no-prefix
services:
foo:
image: ubuntu
bar:
image: nginx
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the docker-compose.yml examples in the issue and review how Compose currently derives names for services and other entities. Define the supported top-level naming scheme and its interaction with per-service container_name values; done means users can select a no-prefix scheme without repeating overrides for every service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100