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

~/.zarf-cache not created on package init #901

Closed
Racer159 opened this issue Oct 13, 2022 · 1 comment · Fixed by #909
Closed

~/.zarf-cache not created on package init #901

Racer159 opened this issue Oct 13, 2022 · 1 comment · Fixed by #909
Labels
bug 🐞 Something isn't working

Comments

@Racer159
Copy link
Contributor

Environment

Device and OS: System76 popOS 22.04
App version: v0.22.0
Kubernetes distro being used: k3d
Other: N/A

Steps to reproduce

  1. Run zarf init without having an init package or ~/.zarf-cache directory
  2. Answer yes to the download

Expected result

Zarf downloads the init package and initializes a cluster

Actual Result

Zarf fails with ERROR: Unable to create the destination file

Visual Proof (screenshots, videos, text, etc)

image

Severity/Priority

High

Additional Context

@Racer159 Racer159 added possible-bug 🐛 bug 🐞 Something isn't working and removed possible-bug 🐛 labels Oct 13, 2022
@RothAndrew RothAndrew moved this to New Requests in Zarf Project Board Oct 13, 2022
@jeff-mccoy
Copy link
Contributor

@Racer159 are you doing a PR to fix this or you want me to?

Noxsios pushed a commit that referenced this issue Oct 13, 2022
## Description
Prevent file download failure when the target directory does not exist

Fixes #901
Repository owner moved this from New Requests to Done in Zarf Project Board Oct 13, 2022
Noxsios pushed a commit that referenced this issue Mar 8, 2023
## Description
Prevent file download failure when the target directory does not exist

Fixes #901
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

Successfully merging a pull request may close this issue.

2 participants