Your message dated Tue, 11 Aug 2020 12:18:27 +0000
with message-id <[email protected]>
and subject line Bug#968207: fixed in libpod 2.0.4+dfsg2-2
has caused the Debian Bug report #968207,
regarding podman: Breaks docker
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
968207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968207
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: podman
Version: 2.0.4+dfsg2-1
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

   * What led up to the situation?

Installing podman or upgrading from 2.0.2+dfsg1-3 to 2.0.3+dfsg1-1
(transcript below, re-testing with 2.0.4

   * What was the outcome of this action?

docker stopped working, in two ways:

 - Users in docker group are no longer able to run docker (permission
   denied).
 - The configured images and containers are no longer available. If they were
   running, they still are, but cannot be controlled any more.

This is because /var/run/docker.sock gets unconditionally redirected to
/run/podman/podman.sock.

   * What outcome did you expect instead?

Since docker.io is not mentioned in Breaks: and since the packages are not
fundamentally inconsistent, I expect them to work together. This is needed at
least to smoothly transition all configured workloads from one to the other.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

Workaround is:

$ sudo dpkg-divert --local --rename --add /usr/lib/tmpfiles.d/podman.conf
$ sudo rm /run/docker.sock
$ sudo systemctl restart docker

Disadvantage is that this restarts any running containers, which might be
undesired at the time.

I suggest creating a podman-docker-compat or similar package with that link,
and also linking /usr/bin/docker to /usr/bin/podman, and breaking docker.io.

-- Transcript:

$ docker ps -a
CONTAINER ID        IMAGE                     COMMAND                  CREATED  
           STATUS                           PORTS               NAMES
7d5e9d7bf3fd        mbsync:latest             "mbsync -a -q"           21 
months ago       Exited (1) 3 minutes ago                             mbsync
$ sudo aptitude install podman  
The following NEW packages will be installed:
  conmon{a} containernetworking-plugins{a} golang-github-containers-common{a} 
podman slirp4netns{a} 
0 packages upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 19.2 MB of archives. After unpacking 93.8 MB will be used.
Do you want to continue? [Y/n/?] 
[…snip install log…]
$ docker ps -a                
Got permission denied while trying to connect to the Docker daemon socket at 
unix:///var/run/docker.sock: Get 
"http://%2Fvar%2Frun%2Fdocker.sock/v1.40/containers/json?all=1": dial unix 
/var/run/docker.sock: connect: permission denied
$ echo $?
1
$ ls -l /run/docker.*         
-rw-r--r-- 1 root root  4 Aug 10 07:01 /run/docker.pid
lrwxrwxrwx 1 root root 23 Aug 10 18:54 /run/docker.sock -> 
/run/podman/podman.sock=

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'oldstable-updates'), (500, 'unstable'), 
(500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: x32, i386

Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages podman depends on:
ii  conmon                           2.0.18-1
ii  containernetworking-plugins      0.8.6-2
ii  crun                             0.14.1+dfsg-1
ii  golang-github-containers-common  0.14.6+ds1-1
ii  init-system-helpers              1.58
ii  libc6                            2.31-2
ii  libdevmapper1.02.1               2:1.02.171-2
ii  libgpgme11                       1.13.1-9
ii  libseccomp2                      2.4.3-1+b1
ii  runc                             1.0.0~rc10+dfsg2-1

Versions of packages podman recommends:
ii  buildah         1.15.0-6
ii  fuse-overlayfs  1.0.0-1
ii  slirp4netns     1.0.1-1
ii  tini            0.18.0-1+b1
ii  uidmap          1:4.8.1-1

Versions of packages podman suggests:
ii  containers-storage  1.21.2+dfsg1-1

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: libpod
Source-Version: 2.0.4+dfsg2-2
Done: Reinhard Tartler <[email protected]>

We believe that the bug you reported is fixed in the latest version of
libpod, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Reinhard Tartler <[email protected]> (supplier of updated libpod package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 11 Aug 2020 07:41:44 -0400
Source: libpod
Architecture: source
Version: 2.0.4+dfsg2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
<[email protected]>
Changed-By: Reinhard Tartler <[email protected]>
Closes: 968207
Changes:
 libpod (2.0.4+dfsg2-2) unstable; urgency=medium
 .
   [ Martin Pitt ]
   * Bump conmon dependency
 .
   [ Dmitry Smirnov ]
   * Harmonize repacksuffix to fix CI.
   * Tighten recommendation on fuse-overlayfs (>= 1.0.0~).
 .
   [ Reinhard Tartler ]
   * Bug fix: "Breaks docker", thanks to Jan Hudec (Closes: #968207).
     - No longer create symlink /run/docker.sock to avoid interfering
       with the docker daemon. Users that wish to replace the docker
       daemon with podman are advised to install the symlink themselves
       and arrange appropriate permissions for podman.sock.
Checksums-Sha1:
 99eec12128b6d275532006f9f7d3ecd46495a52f 5351 libpod_2.0.4+dfsg2-2.dsc
 5d692fb2e15ed06120d6a812ab3903e8325c0b84 12452 
libpod_2.0.4+dfsg2-2.debian.tar.xz
Checksums-Sha256:
 baa26e8713637eb99b720dd1263ea9942566a7b3c4ca3513195784f5f0de641b 5351 
libpod_2.0.4+dfsg2-2.dsc
 a8944e0824cfb1531be9053a1cb279d665f49334d4e3a60d72f168ae8ee053ef 12452 
libpod_2.0.4+dfsg2-2.debian.tar.xz
Files:
 5362d0bf772b00802fecd10a4934b65c 5351 admin optional libpod_2.0.4+dfsg2-2.dsc
 32d5d1a9a5fb605b25f7e02b2224774e 12452 admin optional 
libpod_2.0.4+dfsg2-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAl8yiosUHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQSadpd5QoJsujShAAtXM2/FRZIIRIZheBc5qF/StDC9HT
aAMvIs8mpsN8+bUJIpJ/LAs/L83G7AUbpfJqnNptnJKVjNOUToN4v9IFUMRP/MhI
h8zVGYnuWBVYqvvjxXUCzbnfbQigmb+/P+eaAgFoMtDkU/6IJe5+LH4WxhG4iWva
od4GQFC9q/BCQCTUDhZTpA7Xo5003eCmVUPA9saeKbYvpqrCDFJdtTieeFMWQ9Z+
Ab/QzHJX9sHDODIHnImiK+Bsksp/kBNmumIJrA44UIEr51auHFBiCyTmJjDyXdrD
/fcl+8T84/KwSepRf4NUTxPl9Lv4YXkINhDmeW+cxd+5mp4a5dW2ZXDFCZEPos4d
jbfaLTfvLr4W+g3OC5p8Aig2HA32EcbzrrGQILzFM28N4zzbcz+9LKpgQlgygzPO
EqyXDA+yHTAmplN5rFQHJZe+Cqa00tK4pY4aMJMxAkNJCve5WCGlwAkbVmcMJVdN
RTyDde2ZDKvU+Av8D5vo/3f5i9nD22BIQbLRHxjYB/asOlC3sROzmocN+Bi7gvfa
5fycYdJRudwe0AzFxLWGzqPJlb/Tzjm0GxVozF78xi6V4+XcUr7RBxtDoJZx0c+y
1KguWKLeMwI5AF8l8j5XIbSWLida5jomlAf87Rc2/Wd1C+Wd8kU/7vAwOatzVuuL
GSM2p43RwLT7/Ow=
=bigR
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to