tdnf-automatic upgrade docker and not start service post update
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.2k
- Forks
- 692
- PR merge metrics
- No merged PRs in 30d
Description
Hello, we have recently mounted the latest version of photon os and at the same time we have activated the tdnf-automatic service. This weekend this new VM has carried out an automatic update of the packages, but after updating the docker service, it has not restarted and we have had to perform a systemctl daemon-reload manually. Doesn't the tdnf-automatic service have a configuration file that alerts me to updates and just reports?
Is the problem really from the Docker service
Thanks
?
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 by reviewing the tdnf-automatic and Docker service behavior described in the issue, including the reported need for systemctl daemon-reload after an update. Determine whether the update service supports report-only configuration and whether Docker should restart automatically; done means the behavior and configuration are clearly explained or corrected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, linux
- Domain
- devops, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100