No option to configure docker.io for restart on package upgrade
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
docker.io (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[impact]
docker.io now prompts on upgrade as to whether to restart, which is an improvement, but there is no way to decide ahead of time for a non-interactive upgrade.
[test case]
# apt-get install docker.io
# pgrep dockerd
# dpkg-reconfigure docker.io
< this will only ask a question once the package from proposed is installed >
< choose yes >
# DEBIAN_
# pgrep dockerd
< check dockerd has restarted >
# dpkg-reconfigure docker.io
< choose no >
# DEBIAN_
# pgrep dockerd
< check dockerd has not restarted>
[regression potential]
The change implementing this clearly only affects install/upgrade scenarios: https:/
Also we don't care much about regressions in docker.io! https:/
[original description]
Currently if I run "dpkg-reconfigure docker.io" it doesn't present me with any option to restart the package on upgrade. Looking at the debian post install file, it should, and lp#1668621 suggests it should.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: docker.io 17.03.2-
ProcVersionSign
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Tue Jul 31 10:15:21 2018
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: docker.io
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in docker.io (Ubuntu Xenial): | |
status: | New → Incomplete |
status: | Incomplete → Fix Committed |
Changed in docker.io (Ubuntu Bionic): | |
status: | New → Fix Committed |
Changed in docker.io (Ubuntu Xenial): | |
status: | Fix Committed → In Progress |
status: | In Progress → Triaged |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
tags: |
added: verification-done-xenial removed: verification-needed verification-needed-xenial |
tags: |
added: verification-done-xenial removed: verification-needed verification-needed-xenial |
After chatting, I think the underlying question is how to decide the answer to the restart question when the upgrade is going to be done non-interactively -- and I don't really know the answer to that. Maybe it involves debconf- set-selections?