🌱 use scs capd image while using docker provider #124
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kranurag7
force-pushed
the
kr/use-scs-capd-image
branch
from
079cd56 to
dc37950
Compare
|
@kranurag7 this PR has to be made on "addons" branch. Can you do that? |
kranurag7
force-pushed
the
kr/use-scs-capd-image
branch
from
dc37950 to
b740fa1
Compare
users on fedora using btrfs filesystem were having issues with capd and that was fixed on main and it requires building your own image and using the same here for now. I tested it by building the image locally and now I don't see any error. This will be fixed when we upgrade to 1.6.3 or later version. As of now, we will rely on image built from CAPI main branch and pushed to ghcr.io/sovereigncloudstack/capd with 1.0.5 tag. Signed-off-by: kranurag7 <anurag.kumar@syself.com>
kranurag7
force-pushed
the
kr/use-scs-capd-image
branch
from
b740fa1 to
3b92f88
Compare
janiskemper
approved these changes
Apr 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
users on fedora using btrfs filesystem were having issues with capd and that was fixed on main and it requires building your own image and using the same here for now.
I tested it by building the image locally and now I don't see any error. This will be fixed when we upgrade to 1.6.3 or later version. As of now, we will rely on image built from CAPI main branch and pushed to ghcr.io/sovereigncloudstack/capd with 1.0.5 tag.