Per-user dotfiles #98
Labels
area:ux
UI / UX issue.
comp:agent
Related to Agent component
comp:client
Related to Client component
comp:manager
Related to Manager component
type:feature
Add new features
Milestone
There are many customer requests to preserve the home directory contents, mainly user-installed packages.
The problem is, since our home directories are bind-mounted from each agent's scratch directory, they are not present in Docker images even we perform
docker commit
against running sessions. The technical reasons to use scratch directories are: 1) better I/O performance, 2) agent customization of home directory before starting containers, and 3) enforcement of quota limits.Another problem is that some customer sites do not allow use of per-user vfolders due to their organizational policy, though we are offering auto-mounts of dot-prefixed per-user vfolders (e.g.,
.local
and.ssh
) if present to all sessions (#57) as an alternative to the above problem.This issue tackles the second problem: per-user dotfiles.
For small configuration files aka dotfiles, we could just keep them in the user database and pass them to the agent whenever creating a new container, like SSH keypairs stored in the user database (lablup/backend.ai-manager#211).
This will be exposed as "user settings" in the GUI and CLI.
dotfiles
(max-size limited to 64 KiB) which holds a msgpack'ed list of{"name": "<relative-path-and-file-name>", "perm": "644", "data": "<text-content>"}
to thekeypairs
table..local
directory and the file.ssh/authorized_keys
as they are managed by other means (Per-user packages #99 and Keypair-specific SSH keypair backend.ai-manager#211).dotfiles
from manager to agent viainternal_data
field when creating new kernels.backend.ai user-config dotfiles ...
command set.┆Issue is synchronized with this Asana task by Unito
The text was updated successfully, but these errors were encountered: