Closed capsulecorplab closed 5 months ago
@thomas-bc sorry to bug you again, but it seems ghcr needs to be enabled for the fprime-community. Otherwise, the CI pipeline needed to publish images is broken https://github.com/fprime-community/fprime-workspace-image/actions/runs/7404465060/job/20146022620#step:6:328
They seem to be enabled already... I'm assuming the token in the repository secrets is yours? I wonder if maybe that could be it - I'll try to replace it with another token. Sorry for the delay, I've been busy with other things. I'll get back to this as soon as I can
They seem to be enabled already... I'm assuming the token in the repository secrets is yours? I wonder if maybe that could be it - I'll try to replace it with another token. Sorry for the delay, I've been busy with other things. I'll get back to this as soon as I can
No worries. Yeah, I generated the personal access token and added it as a repo secret; that could likely be the issue... If it helps, here are my notes on how I set up GHCR for my other Kasm workspaces https://gist.github.com/capsulecorplab/75b930c42188006ed56a3785aa797971
@capsulecorplab some updates:
ghcr.io/fprime-community/...
🎉 Question, what makes the image so large? Seems the base image is only a couple hundred MB, where this is in the order of ~10GB ?
Let me know if you have any thoughts/comments on the above
Thanks, @thomas-bc ! Closing this issue as per the fantastic updates from #49!
As for the image size, I suspect the Arduino board package indexes could be contributing to a good portion of the image space, as I've also witnessed the same happen in one of my other IIaC workspaces. Though, not entirely sure why it's in the order of ~10GB
Opened #51 as a reminder to investigate the disk space usage
follow-up to #33