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

Using a relative path for KITOPS_HOME interacts strangely with context path in pack #381

Closed
amisevsk opened this issue Jun 25, 2024 · 0 comments · Fixed by #382
Closed
Labels
bug Something isn't working

Comments

@amisevsk
Copy link
Contributor

Describe the bug

Setting KITOPS_HOME to a relative path and running kit pack with an alternate context directory will result in KITOPS_HOME resolving within that context directory instead of the directory you're calling kit from. This leads to strange behaviour, where after building a modelkit, it will not be visible in kit list

To Reproduce

  1. Set KITOPS_HOME=.kitops-storage
  2. Pack a modelkit using a context path: kit pack -t <tag> ./path/to/model
  3. Path .kitops-storage is created, but does not contain blobs; kit list returns nothing
  4. Note that ./path/to/model/.kitops-storage has been created and contains the blobs

Version
nightly

Additional context
N/A

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.

1 participant