Arch Linux

*Description:*

After upgrading docker package (among with others) to latest 1:19.03.12-2 I started to get following errors on any `docker build` or `docker pull` commands:

```
$ docker pull node
Using default tag: latest
latest: Pulling from library/node
419e7ae5bb1e: Already exists
848839e0cd3b: Already exists
de30e8b35015: Already exists
258fdea6ea48: Already exists
ddb75eb7f1e9: Already exists
7ec8a0667334: Already exists
c6d8dab5779d: Extracting [==================================================>] 34.68MB/34.68MB
d3ae9be01b42: Download complete
38ff96b6f833: Download complete
failed to register layer: Error processing tar file(exit status 1): Error cleaning up after pivot: remove /.pivot_root223330811: device or resource busy
```

Next attempts failing immediately:

```
$ docker pull node
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
```

The only info I can found in journalctl is:

```
Aug 19 12:22:43 Envek-NUC dockerd[1353]: time="2020-08-19T12:22:43.526767832+03:00" level=info msg="Attempting next endpoint for pull after error: failed to register layer: Error processing tar file(exit status 1): Error cleaning up after pivot: remove /.pivot_root277226559: device or resource busy"
```

*Additional info:*

package versions:
docker 1:19.03.12-2
containerd 1.3.4-2

upstream bug report:
https://github.com/moby/moby/issues/40008#issuecomment-676047593 (they says that it may be caused by too new version of golang used to build the package: 1.14 has known issues)

older reports:
https://bugs.archlinux.org/task/58690 — was caused by some “custom setup”, but my setup is as typical as possible, I believe.

Environment: Manjaro Linux 20.1 kernel 4.19.138-1-MANJARO

Disk usage (both space and inodes) is OK.

Package reinstall didn't help.

*Steps to reproduce:*

```
docker pull node
```