Open dnmvisser opened 2 months ago
My best guess is that this is related to the struggles I see a lot with these older i386 distributions/versions, especially around 64bit inodes -- FWIW, your example seems to work fine for me without any modification to the image:
$ docker run -it --rm debian/eol:slink
Unable to find image 'debian/eol:slink' locally
slink: Pulling from debian/eol
2350dc7f78f9: Pull complete
Digest: sha256:8a6513d46960af71f6e534b294a31fdd09522220f4ee4df1629720d2c1d0d529
Status: Downloaded newer image for debian/eol:slink
bb0db2d4f72d:/# apt-get update
Get:1 http://archive.debian.org slink/main Packages [493kB]
Get:2 http://archive.debian.org slink/main Release [93B]
Fetched 494kB in 0s (786kB/s)
Reading Package Lists...
Building Dependency Tree...
bb0db2d4f72d:/# apt-get install -y tree
Reading Package Lists...
Building Dependency Tree...
The following NEW packages will be installed:
tree
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 12.7kB of archives. After unpacking 31.7kB will be used.
Get:1 http://archive.debian.org slink/main tree 1.2-6 [12.7kB]
Fetched 12.7kB in 0s (37.2kB/s)
Selecting previously deselected package tree.
(Reading database ... 2644 files and directories currently installed.)
Unpacking tree (from .../archives/tree_1.2-6_i386.deb) ...
Setting up tree (1.2-6) ...
bb0db2d4f72d:/# tree /tmp/
/tmp/
0 directories, 0 files
I'm not sure this is the right location to report, but apt/dpkg is broken in slink:
I played around a bit, and it appears to a permission issue on the reported directory. If I make that directory group writable, all seems to be OK:
Not sure if this is the correct approach, but it is much more usable if pacakges can be installed....