GitHub Actions runners face 404 error during concurrent builds

I am surprised that even a single docker instance works with the data-root /var/lib/docker being on an EFS volume (=nfs remote share).

Is it safe to assume that you missed the GitHub Actions cache documentation?