Why is `Container.name` optional and not always a `str`?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.2k
- Forks
- 1.7k
- Avg merge
- 13d 8h
- Merged PRs (30d)
- 2
Description
Maybe I'm missing something but from what I know a container must always have a name... when can it be null?
See https://github.com/docker/docker-py/blob/main/docker/models/containers.py#L33-L34
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 docker/models/containers.py at lines 33-34 and check the Docker Engine API representation for a container name. Determine whether the optional, non-str annotation matches the API behavior; done means the issue's question is resolved and the annotation or its rationale is consistent with the evidence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100