Moby: Docker kann nicht deinstalliert werden, wenn es nie funktioniert hat (Ubuntu)

Erstellt am 14. Mai 2013  ·  3Kommentare  ·  Quelle: moby/moby

Die Deinstallation schlägt fehl, weil das Skript prerm die Docker-Instanz nicht stoppen kann (weil keine ausgeführt wird):

root<strong i="7">@hv</strong> ~ # aptitude purge lxc-docker
The following packages will be REMOVED:  
  lxc-docker{p} 
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B of archives. After unpacking 4,483 kB will be freed.
Do you want to continue? [Y/n/?] 
(Reading database ... 56846 files and directories currently installed.)
Removing lxc-docker ...
stop: Unknown instance: 
dpkg: error processing lxc-docker (--purge):
 subprocess installed pre-removal script returned error exit status 1
docker start/running, process 11949
Errors were encountered while processing:
 lxc-docker
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:

Dieses Skript verursacht das Problem /var/lib/dpkg/info/lxc-docker.prerm ( docker/packaging/ubuntu/lxc-docker.prerm )

#!/bin/sh

# Stop docker
/sbin/stop docker

Das Skript sollte nur versuchen, Docker zu stoppen, wenn eine Instanz ausgeführt wird.

Hilfreichster Kommentar

Ich hatte fast das gleiche Problem unter Ubuntu 12.04.

Fehler

# apt-get purge lxc-docker 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following package was automatically installed and is no longer required:
  bsdtar
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  lxc-docker*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 4,753 kB disk space will be freed.
Do you want to continue [Y/n]? y
(Reading database ... 235601 files and directories currently installed.)
Removing lxc-docker ...
stop: Unknown instance: 
dpkg: error processing lxc-docker (--purge):
 subprocess installed pre-removal script returned error exit status 1
docker start/running, process 1841
Errors were encountered while processing:
 lxc-docker
localepurge: Disk space freed in /usr/share/locale: 0 KiB
localepurge: Disk space freed in /usr/share/man: 0 KiB
localepurge: Disk space freed in /usr/share/gnome/help: 0 KiB
localepurge: Disk space freed in /usr/share/omf: 0 KiB

Total disk space freed by localepurge: 0 KiB

E: Sub-process /usr/bin/dpkg returned an error code (1)

Um das zu umgehen, habe ich einfach einen schmutzigen Trick gemacht, /sbin/stop docker im Pre-Removal-Skript /var/lib/dpkg/info/lxc-docker.prerm und es ging durch.

Alle 3 Kommentare

Danke, Daniela!. Guter Fang. Dies wurde im Debian-Paket gemacht, ich werde dies korrigieren.

Ich hatte fast das gleiche Problem unter Ubuntu 12.04.

Fehler

# apt-get purge lxc-docker 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following package was automatically installed and is no longer required:
  bsdtar
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  lxc-docker*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 4,753 kB disk space will be freed.
Do you want to continue [Y/n]? y
(Reading database ... 235601 files and directories currently installed.)
Removing lxc-docker ...
stop: Unknown instance: 
dpkg: error processing lxc-docker (--purge):
 subprocess installed pre-removal script returned error exit status 1
docker start/running, process 1841
Errors were encountered while processing:
 lxc-docker
localepurge: Disk space freed in /usr/share/locale: 0 KiB
localepurge: Disk space freed in /usr/share/man: 0 KiB
localepurge: Disk space freed in /usr/share/gnome/help: 0 KiB
localepurge: Disk space freed in /usr/share/omf: 0 KiB

Total disk space freed by localepurge: 0 KiB

E: Sub-process /usr/bin/dpkg returned an error code (1)

Um das zu umgehen, habe ich einfach einen schmutzigen Trick gemacht, /sbin/stop docker im Pre-Removal-Skript /var/lib/dpkg/info/lxc-docker.prerm und es ging durch.

@dbankk , @terrywang Könnten Sie überprüfen, ob der folgende Patch für Sie funktioniert?

41cdd9b

War diese Seite hilfreich?
0 / 5 - 0 Bewertungen