how-to WORKSPACE_SYNC

[pvp-by]

my step :

use runpod template

ghcr.io/ai-dock/comfyui:latest
without PROVISIONING_SCRIPT
WORKSPACE_SYNC first time true , after true/false result down

result :

• system logs:

  2024-02-29T07:57:13Z create pod network
  2024-02-29T07:57:13Z create container ghcr.io/ai-dock/comfyui:latest
  2024-02-29T07:57:14Z latest Pulling from ai-dock/comfyui
  2024-02-29T07:57:14Z Digest: sha256:47f033dddfba20771da60cfc3bc403812f88cb5b3b03ce6e17de7fa9272e3a50
  2024-02-29T07:57:14Z Status: Image is up to date for ghcr.io/ai-dock/comfyui:latest
  2024-02-29T07:57:14Z start container

• container logs:

  ...
  2024-02-29T07:51:18.335204123Z 
  2024-02-29T07:51:18.626160221Z chown: changing ownership of '/workspace/': Operation not permitted
  2024-02-29T07:51:18.653602734Z chown: changing ownership of '/workspace//.ai-dock-permissions-test': Operation not permitted
  2024-02-29T07:51:19.416355191Z chown: changing ownership of '/workspace/home/user': Operation not permitted
  2024-02-29T07:51:19.451593327Z useradd: warning: the home directory /workspace/home/user already exists.
  2024-02-29T07:51:19.451656302Z useradd: Not copying any file from skel directory into it.
  2024-02-29T07:51:19.529256483Z usermod: group 'render' does not exist
  2024-02-29T07:51:19.534188717Z usermod: group 'sgx' does not exist
  2024-02-29T07:51:19.544032612Z mkdir: cannot create directory ‘/workspace/home/user/.ssh’: File exists
  2024-02-29T07:51:19.551713395Z cp: not writing through dangling symlink '/workspace/home/user/.ssh'
  2024-02-29T07:51:19.559099834Z chown: changing ownership of '/workspace/home/user/.ssh': Operation not permitted
  2024-02-29T07:51:19.566694095Z chmod: cannot access '/workspace/home/user/.ssh/authorized_keys': No such file or directory
  2024-02-29T07:51:19.589076075Z chmod: cannot access '/home/user-linux/.ssh/authorized_keys': Too many levels of symbolic links

my goal install comfyui deps and when run, only extract docker image. save my install deps for custom_nodes.

first time i need use WORKSPACE_SYNC as true or false for everytime save my install deps

PS whether it's important to use any PROVISIONING_SCRIPT or can broken link ?

[robballantyne]

You can ignore the permissions errors they are not serious but I'll handle them in the next build.

To use sync, you'll need to run with WORKSPACE_SYNC=true on every run. Files will only be moved the first time but symlinks are created on subsequent runs.

You need to be aware that syncing to RunPod network volumes can be incredibly slow. It will also consume a great deal more space on the volume than it does in the container.

Provisioning is optional, but recommended. Any models it downloads will persist to the volume and it's useful for installing dependecies

[pvp-by]

@robballantyne Thank you so much for the clarification, you have confirmed the approach I need and that I am correct in my understanding of what is going on. If you ignore the current permissions, then it doesn't seem so bad.

and one more small clarification, is there a mechanism or is it planned some kind of similar PROVISIONING_SCRIPT, but its location is allowed on the network disk (the same workspace), i.e. when I want to apply such a script.

its own and without the extra cost of micro hosting for the script (even github)

it would be convenient to have such an argument (or functionality) that the workspace itself can be the source (even if the order of execution of such a script is the last)

[robballantyne]

You can run without declaring a provisioning script and the container will still look for, and execute the file /opt/ai-dock/bin/provisioning.sh so if you can get the file into that location by whatever alternative means it is possible.

You can also place a non executable file(s) in /opt/ai-dock/bin/preflight.d which will be sourced as part of the init.sh procedure at startup.

I can probably make this easier by having the init procedure test for a file on the workspace volume at container start.

[robballantyne]

Manually run venv-sync comfyui at any time