-
Notifications
You must be signed in to change notification settings - Fork 47
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
[BUG] Can't package map because of non-exising docker build cache #469
Comments
@jordimassaguerpla Thanks for reporting this issue as well as the investigation. The PR will be handled in the Holoscan SDK, though unfortunately nvidia-holoscan is read only, pushed from Nvidia internal gitlab repo. The fix will then have to wait till the next public release of Holoscan SDK, ETA Jan, 2024. |
@jordimassaguerpla, another option to try is to specify the cache location, setting it to a writable directory using |
when using monai-depoy package command use | # Copy user-specified MONAI Deploy SDK file use sub option ----monai-deploy-sdk-file monai_deploy_app_sdk-0.6.0-py3-none-any.whl with monai-deploy package command like monai-deploy package simple_imaging_app -c simple_imaging_app/app.yaml -t {tag_prefix}:1.0 --platform x64-workstation --monai-deploy-sdk-file monai_deploy_app_sdk-0.6.0-py3-none-any.whl -l DEBUG i will work |
Describe the bug
I am trying to package an example map inside a github action. However, I am getting this error:
See workflow file and terraform file
Looks very similar at this bug docker/buildx#206 . However, according to that bug, this is supposed to be fixed in buildx already.
Could you help me?
Steps/Code to reproduce bug
I am having this issue when running the package subcommand inside a vm in Azure, which is deployed using terraform inside of a github action.
The vm is Ubuntu-22_04-lts, thus in principle you should be able to reproduce it on a fresh install of Ubuntu-22_04-lts. The issue seems to be that, when you run the package subcommand, it uses a --from-cache and --to-cache options when there is not yet a cache. If you run it twice, the second time it will find a cache, so it is super important to run it on a fresh install.
You can see the exact commands in the github action jordimassaguerpla@279dcbd
I have tried using the "--no-cache" flag of the package subcommand, but I get the same behaviour.
Expected behavior
The package subcommand should not try to use cache if you specify the "--no-cache" flag.
Environment details (please complete the following information)
The text was updated successfully, but these errors were encountered: