Docker not binding message file

[kriskowal]

On a Mac, using Colima as Dockerd, when running yarn test -m upgrade-next --debug in agoric-sdk/a3p-integration, I encounter a failure because the temporary file purported to contain a MoTD for the image does not exist.

docker: Error response from daemon: invalid mount config for type "bind": bind source path does not exist: /var/folders/90/tx2ns4xs1vb4bhzzld6hp2dr0000gn/T/upgrade-next-2559-ItRYc0sgkd9y.
See 'docker run --help'.
Run of ghcr.io/agoric/agoric-3-proposals:test-upgrade-next failed with exit code 125
file:///.../a3p-integration/node_modules/@agoric/synthetic-chain/dist/cli/cli.js:666

[turadg]

Does it work in dockerd from Docker Inc?

[mhofman]

Might also be a permission problem. MacOS is pretty finicky on those.

[kriskowal]

Does it work in dockerd from Docker Inc?

I will have to rely on others to verify. I’m using Colima not by choice, but because Dockerd converges on a working system only if you upgrade Dockerd before you upgrade a particular Mac OS Software Update, and I unwittingly did them in the wrong order. I’ve not yet found a working mitigation, and have tried several.