Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nitric up results in a docker error "failed to load cache key: invalid response status 403" #709

Open
jyecusch opened this issue Dec 16, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@jyecusch
Copy link
Member

jyecusch commented Dec 16, 2024

Bug Report

Issue

When running nitric up using one of the Nitric Pulumi Providers and recent versions of Docker Desktop an error is thrown when attempting to build the cloud specific container images.

Error Output:

Diagnostics:
  docker:index:Image (hello_services-hello-image):
    error: error reading build output: failed to read downloaded context: failed to load cache key: invalid response status 403

  pulumi:pulumi:Stack (hello-hello-dev):
    time="2024-12-15T18:38:28-05:00" level=error msg="Can't add file /private/var/folders/_n/vzhc6dhn4gd4mqbp2k_srtqm0000gn/T/build-hello_services-hello/runtime to tar: io: read/write on closed pipe"
    time="2024-12-15T18:38:28-05:00" level=error msg="Can't close tar writer: io: read/write on closed pipe"

Steps

Steps to reproduce the behavior:

  1. Install Docker Desktop
  2. Create a nitric project
  3. Create a new stack for the project targeting AWS with the standard Pulumi provider
  4. Run nitric up

Expected

The containers build and the deployment succeeds without errors

Environment and setup information

  • Nitric CLI Version: 1.55.12
  • Provider: nitric/[email protected]
  • Docker Desktop v4.36.0 (175267) (engine version 27.3.1) (API version 1.47)
@jyecusch jyecusch added the bug Something isn't working label Dec 16, 2024
@jyecusch
Copy link
Member Author

I've also found recent issues with similar errors related to Terraform (also using Docker Desktop on MacOS): https://stackoverflow.com/questions/79267868/docker-image-build-fails-in-terraform-failed-to-read-downloaded-context-faile

@jyecusch
Copy link
Member Author

jyecusch commented Dec 16, 2024

The current workaround is to disable containerd in Docker Desktop or use another machine for cloud deployments (e.g. GitHub Actions running linux)

Settings_-_Docker_Desktop

@jyecusch jyecusch self-assigned this Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants
@jyecusch and others