CDI: dockerd logs warnings on startup for missing CDI directories
Open
Nobody has claimed this yet.
area/daemon
area/packaging
kind/feature
- Dominant language
- Go
- Stars
- 72.1k
- Forks
- 19.2k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 164
Description
Description
On a fresh install of docker 28.2.0-rc.2, the daemon logs warnings during startup because the directories to monitor are missing;
INFO[2025-05-26T10:47:59.604012692Z] Initializing buildkit
WARN[2025-05-26T10:47:59.604834418Z] CDI setup error /etc/cdi: failed to monitor for changes: no such file or directory
WARN[2025-05-26T10:47:59.604873373Z] CDI setup error /var/run/cdi: failed to monitor for changes: no such file or directory
We should
- verify what the behavior is if these directories are created while the daemon is running, and if they are monitored for changes.
- If it's not monitoring during the daemon's lifecycle, we should consider updating our packaging to create the directories at startup, similar to https://github.com/docker/docker-ce-packaging/pull/841
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 daemon's CDI setup and the docker-ce-packaging change linked in the issue. Verify whether creating /etc/cdi or /var/run/cdi while dockerd runs begins monitoring and whether changes are detected. Done means the fresh-install startup warnings and lifecycle behavior are addressed, with the relevant behavior covered by tests or packaging changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100