cannot purge docker.io due to a bashism in nuke-graph-directory

Bug #1724353 reported by Fensminger on 2017-10-17
36
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Docker.io
Fix Released
Unknown
docker.io (Debian)
Fix Released
Unknown
docker.io (Ubuntu)
Medium
Unassigned

Bug Description

i made sudo apt-get purge docker.io

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: docker.io (not installed)
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
AptOrdering:
 docker.io:amd64: Purge
 NULL: ConfigurePending
 NULL: PurgePending
 NULL: ConfigurePending
Architecture: amd64
Date: Tue Oct 17 21:30:56 2017
ErrorMessage: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 127
InstallationDate: Installed on 2017-10-08 (9 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt 1.5
SourcePackage: docker.io
Title: package docker.io (not installed) failed to install/upgrade: le sous-processus script post-removal installé a retourné une erreur de sortie d'état 127
UpgradeStatus: No upgrade log present (probably fresh install)

Fensminger (fensminger) wrote :
Brian Murray (brian-murray) wrote :

nuke-graph-directory.sh uses /bin/sh which is dash and shopt is not available in dash.

/var/lib/docker/nuke-graph-directory.sh: 64: /var/lib/docker/nuke-graph-directory.sh: shopt: not found

Changed in docker.io (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
summary: - package docker.io (not installed) failed to install/upgrade: le sous-
- processus script post-removal installé a retourné une erreur de sortie
- d'état 127
+ cannot purge docker.io due to a bashism in nuke-graph-directory
Changed in docker.io (Debian):
status: Unknown → New
Anders Kaseorg (andersk) wrote :

This was fixed in Debian a few releases ago (1.13.0~ds1-2), but Ubuntu hasn’t merged this package from Debian since over a year ago (1.11.2~ds1-6).

Changed in docker.io (Debian):
status: New → Fix Released
Andreas Hasenack (ahasenack) wrote :
tags: added: bitesize server-next
Changed in docker.io:
status: Unknown → Fix Released
Robie Basak (racb) on 2018-04-13
tags: added: server-next-drop
Robie Basak (racb) on 2018-05-02
tags: removed: server-next-drop
Andreas Hasenack (ahasenack) wrote :

Turns out there was another bug about this issue, and it was fixed in bionic:

docker.io (17.03.2-0ubuntu2) bionic; urgency=medium
  * Replace "--no-restart-on-upgrade" with "--no-start" and a debconf prompt
    - not restarting Docker causes many issues (LP: #1658691)
    - suggested methods for keeping containers up are to use a restart policy
      ("--restart=..." on "docker run"), Swarm Mode services, or rolling
      replacement of k8s workers
  * Backport 30519 for bashism (LP: #1744599)

Xenial and Artful are still affected.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.