You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ticket #51 investigated how to store the Notebooks persistent, in case of Docker Container removal, resulting in the proposal to use Docker VOLUMES for notebook files and secret store entries.
The current idea is to support 2 scenarios
S1) AI-Lab manages the data anonymously and encapsulated
S2) user (partially) modifies the data, keeps a copy of the data and provides the data when using the AI-Lab
Ticket #51 investigated how to store the Notebooks persistent, in case of Docker Container removal, resulting in the proposal to use Docker VOLUMES for notebook files and secret store entries.
The current idea is to support 2 scenarios
Following the results of ticket #51:
$MOUNT
inside the Docker Container, which implements scenario S1.$MOUNT
when starting the Docker Containerentrypoint.py
(as always)entrypoint.py
copies the data from$BACKUP
to$MOUNT
$MOUNT
$BACKUP
$MOUNT
as the experiments in ticket Investigate how to store the Notebooks persistent, in case of Docker Container removal #51 showed.The current ticket therefore requests to
VOLUME
directive toDockerfile
For mounting a Docker volume please do not add a slash as prefix to the volume name.
-v /host:/container
mounts host directory/host
-v vol:/container
mounts Docker volumevol
The mount point inside the Docker container in both cases is
/container
.The text was updated successfully, but these errors were encountered: