What this error means

mount /home/runner/.local/share/containers/storage/overlay:...: permission denied is a Docker failure pattern reported for developers trying to fix docker rootless overlay mount failure in github actions ci runner environment causing manifest generation to fail. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

docker-nixpkgs PR #104 (May 20, 2026): GitHub Actions runner suddenly breaks rootless overlay mount for Podman containers. Workaround is switching to vfs storage driver. Error blocks CI pipelines generating container images. Covers both the overlay mount error and related unixgram permission denied errors in GHA environment.

Common causes

  • docker-nixpkgs PR #104 (May 20, 2026): GitHub Actions runner suddenly breaks rootless overlay mount for Podman containers. Workaround is switching to vfs storage driver. Error blocks CI pipelines generating container images. Covers both the overlay mount error and related unixgram permission denied errors in GHA environment.

Quick fixes

  1. Confirm the exact error signature matches mount /home/runner/.local/share/containers/storage/overlay:...: permission denied.
  2. Check the Docker account, local tool state, and provider configuration involved in the failing workflow.
  3. Verify the model name, local service connectivity, and network access before retrying the model pull.

Platform/tool-specific checks

  • Verify the command, editor, extension, or API client that produced the error.
  • Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
  • Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

  1. Capture the exact error message and the command, editor action, or request that triggered it.
  2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
  3. Review the source evidence below and compare it with your environment.
  4. Apply one change at a time and rerun the smallest failing action.
  5. Keep the working fix documented for the team or deployment environment.

How to prevent it

  • Keep provider/tool configuration documented.
  • Record non-secret diagnostics such as tool version, provider name, model name, and command path.
  • Add a lightweight check before CI or production workflows depend on the tool.