You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Set KITOPS_HOME=.kitops-storage
Pack a modelkit using a context path: kit pack -t <tag> ./path/to/model
Path .kitops-storage is created, but does not contain blobs; kit list returns nothing
Note that ./path/to/model/.kitops-storage has been created and contains the blobs
Version
nightly
Additional context
N/A
The text was updated successfully, but these errors were encountered:
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 inkit list
To Reproduce
KITOPS_HOME=.kitops-storage
kit pack -t <tag> ./path/to/model
.kitops-storage
is created, but does not contain blobs;kit list
returns nothing./path/to/model/.kitops-storage
has been created and contains the blobsVersion
nightly
Additional context
N/A
The text was updated successfully, but these errors were encountered: