Install SDK from a local file is not supported when XDS-server is running in the VM
Fixed
Description
For now, when a user want to install a SDK from a local file (using command xds-cli sdks install -f $HOME/xds-workspace/sdks/my_sdk.sh), this file must be located in $HOME/xds-workspace/sdks.
This doing well when xds-server is running in a docker container because by default $HOME/xds-workspace/sdks directory is shared using --volume dokcer option.
But it's not working when xds-server is running in the VM downloadable here, see also doc here
Several solutions exist to fix that problem :
add vbox-addon in VM and auto mount XDS-Workspace shared point OR
rely on Syncthing to share $HOME/xds-workspace/sdks directories OR
update sdks code to remove restriction about $HOME/xds-workspace/sdks (see file sdks.go line 352)
Environment
None
Activity
Show:
Details
Assignee
Clément Bénier
Clément Bénier
Reporter
Sebastien Douheret
Sebastien Douheret
Labels
Contract ID
Priority
Major
Created October 5, 2018 at 9:51 AM
Updated April 8, 2021 at 4:29 PM
Resolved April 8, 2021 at 4:28 PM
Flag notifications
Something's gone wrong
Looks like you've been signed out. Try logging in again.
Major
For now, when a user want to install a SDK from a local file (using command xds-cli sdks install -f $HOME/xds-workspace/sdks/my_sdk.sh), this file must be located in $HOME/xds-workspace/sdks.
This doing well when xds-server is running in a docker container because by default $HOME/xds-workspace/sdks directory is shared using --volume dokcer option.
But it's not working when xds-server is running in the VM downloadable here, see also doc here
Several solutions exist to fix that problem :
add vbox-addon in VM and auto mount XDS-Workspace shared point
OR
rely on Syncthing to share $HOME/xds-workspace/sdks directories
OR
update sdks code to remove restriction about $HOME/xds-workspace/sdks (see file sdks.go line 352)