[docker] Switch to kube-compatible plugin path for images #3653
+23
−19
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
marun
force-pushed
the
xsvm-plugin-path
branch
from
479dccc to
ddb3655
Compare
marun
changed the title
marun
force-pushed
the
xsvm-plugin-path
branch
from
ddb3655 to
c274f20
Compare
When attempting to deploy the xsvm docker image to kube, it became apparent that an image using the default plugin dir (~/.avalanchego/plugins) isn't compatible with kube due to permission issues. Switching to /avalanchego/build/plugins (the path used by subnet-evm) ensures compatibility with kube.
marun
force-pushed
the
xsvm-plugin-path
branch
from
c274f20 to
9b8135a
Compare
marun
changed the title
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.
Why this should be merged
In attempting to deploy the xsvm docker image to kube, it became apparent that an image using the default plugin dir (
~/.avalanchego/plugins) wasn't compatible with execution in kube due to permission issues.How this works
/avalanchego/build/pluginsHow this was tested
CI
Need to be documented in RELEASES.md?
N/A