≡ menu
× menu

cnnmmd

Usage: Container (Docker): Storage

In the case of Windows and macOS, containers run in a virtual environment, so you will need to allocate storage space for them.

Basically, the storage space used by a virtual environment increases as you use it - so it won't be a problem at first, but you can't reduce it - you might want to set a limit on usage, so here are some estimates for the total storage space when using this tool on Linux (Ubuntu) in WSL2: [※1][※2]

・
16 - 18 GB ... Use the CPU containers for trial purposes
・
32 - 36 GB …… Use CPU containers to a certain extent
・
64 - 70 GB …… Use a fair amount of GPU containers

There is a big difference in size between the CPU and GPU containers. This is because the GPU-related files (Pytorch's CUDA-related files) are very large. The difference in size between containers with the same environment is as follows:

・
2-3 GB ... if the container is designed for CPU
・
10 GB - if you create a container for GPU
*1
You can shrink the unused space by backing up and restoring the virtual environment, but this is a bit of a hassle (on macOS, you can also reduce it from the Docker Desktop UI, depending on the state of the virtual environment).
*2
For WSL2, the storage limit for the virtual environment can be specified in the following file directly under the user folder: .wslconfig (defaultVhdSize)

Usage: Container (Docker): Permissions

This tool mounts some folders from the container to the host (PC) side. If you are using a container with the following permissions, you may get an alert when extracting files to the tool itself (e.g., "Files cannot be accessed") depending on the behavior of the application you are using: [*1]

・
Change the group permissions of the container and run it as a normal user (usermod -aG docker ...)

Even in this case, it will not affect your actual usage - just run it with the following permissions and the alert will go away: [※2]

・
Run a container as a normal user using rootless (rootless docker)
・
Running in a desktop-compatible container (Docker Desktop)
・
Run the container as administrator (root)
*1
This occurs due to the difference in permissions between the app running in the container and the host (PC) permissions that run the container.
*2
However, if you run the container with administrator (root) privileges, you may encounter file sharing issues - in particular, when trying to retrieve files on the WSL2 side from the Windows side (for example, the ComfyUI workflows included in the plugin), you may not be able to view them due to permission issues (in this case, you can simply relax the permissions for the folder from the Linux side of WSL2).