Limitations

1. Disk persistency

On SavviHub workspace, /home/vessl is the only persistent directory. Other directories reset every time you restart a workspace. If you need libraries or packages that should be installed outside /home/vessl, fill the init script with the install commands, otherwise you can build your own docker image on top of SavviHub managed docker images (Debian base images are compatible).
Init Script example

2. File owners (managed cluster only)

On managed cluster, Amazon EFS is mounted to /home/vessl and owners and groups of all files inside this directory are managed by Amazon EFS. So they are not vessl, they are a random number like 50024. This can be problematic in some cases. For example, vim creates .viminfo file with permission 600, however, because its owner is not vessl, vim cannot write to .viminfo. In this case, chmod o+w .viminfo should be run.

3. Docker not supported

Since SavviHub workspaces run on Kubernetes, they are basically docker containers. Docker daemon inside a docker container is not supported unless it is privileged. SavviHub does not support privileged containers for security reasons.
Last modified 2mo ago