Comment 2 for bug 1797114

More precisions:

Two containers, two different ways to react. One is working as expected, while the second one does NOT.

Skopeo versions are the same:
skopeo-0.1.31-1.gitf9baaa6.el7.x86_64
skopeo-containers-0.1.31-1.gitf9baaa6.el7.x86_64

Failing container:
mistral_engine (192.168.24.1:8787/tripleomaster/centos-binary-mistral-engine:965941f1e62cef16967e7a7cd6d98263e52acb62_0989b280-updated-20181010112921)

Working container:
mistral_api (192.168.24.1:8787/tripleomaster/centos-binary-mistral-api:965941f1e62cef16967e7a7cd6d98263e52acb62_0989b280-updated-20181010112921)

The full error is:
2018-10-10 12:53:48 | Error inspecting image: docker://docker.io/tripleomaster/centos-binary-cron:965941f1e62cef16967e7a7cd6d98263e52acb62_0989b280
2018-10-10 12:53:48 | time="2018-10-10T12:53:46Z" level=fatal msg="error getting username and password: error reading JSON file "/run/containers/42430/auth.json": error unmarshaling JSON at "/run/containers/42430/auth.json": unexpected end of JSON input"

The /run/containers directory does not exist in the working container, while it DOES exist in the failing container.

Main difference: /run is bind-mounted in the failing container, while NOT in the working one.

Question: is the bind-mount requested? :)