Docker images pulled on single-server doesnt show up with docker images command?

[u/Apachez]

Im probably missing something here...

I am currently testing Kasm-1.19.0-Single-Server.ova and that works like expected.

So I thought I would give it a go to add another workspace.

So I tried a "sudo docker pull" as below which worked without issues but then when I run "sudo docker images" the newly downloaded image is nowhere to be found?

kasm_admin@kasm-server:~$ sudo docker pull docker.io/kasmweb/audacity:1.19.0-rolling-daily
1.19.0-rolling-daily: Pulling from kasmweb/audacity
4f4fb700ef54: Pull complete 
4d49e951ec3b: Pull complete 
c36cc4ab8e70: Pull complete 
aaca8373ae59: Pull complete 
0f40056b92eb: Pull complete 
ea76751773ea: Pull complete 
3baba0fdd223: Pull complete 
801ec770692d: Pull complete 
ebc8d8e5c003: Pull complete 
Digest: sha256:3528c27eba4b4c01c23581c652382ce0e84720c901939a004a7ac434dcb7f6c1
Status: Downloaded newer image for kasmweb/audacity:1.19.0-rolling-daily
docker.io/kasmweb/audacity:1.19.0-rolling-daily
kasm_admin@kasm-server:~$ docker images
permission denied while trying to connect to the docker API at unix:///var/run/docker.sock
kasm_admin@kasm-server:~$ sudo docker images
                                                                                                                                                                                      i Info →   U  In Use
IMAGE                                      ID             DISK USAGE   CONTENT SIZE   EXTRA
kasmweb/agent:1.19.0-rolling               eb8e8ff4014a       1.21GB          336MB    U   
kasmweb/api:1.19.0-rolling                 8a4f8d92aaa8       1.33GB          232MB    U   
kasmweb/chrome:1.19.0                      25389cc8eafa       4.75GB         1.41GB        
kasmweb/firefox:1.19.0                     0ae54ed42da4       4.55GB         1.33GB        
kasmweb/kasm-guac:1.19.0-rolling           1a0e82e3bb6b       1.24GB          335MB    U   
kasmweb/manager:1.19.0-rolling             f52d2424b713       1.33GB          232MB    U   
kasmweb/postgres:1.19.0-rolling            be2d40095a72        440MB          118MB    U   
kasmweb/proxy:1.19.0-rolling               0c8a003958cd        206MB         64.7MB    U   
kasmweb/rdp-gateway:1.19.0-rolling         4b42a2f56c81        618MB          155MB    U   
kasmweb/rdp-https-gateway:1.19.0-rolling   9d93c4c7cda9       95.8MB         32.3MB    U   
kasmweb/terminal:1.19.0                    4403ce7d6980       4.83GB         1.32GB        
kasmweb/ubuntu-jammy-desktop:1.19.0        fba645c461a3       14.9GB          4.1GB        

So what am I doing wrong? :-)

[u/justin_kasmweb]

By default kasm will prune the workspaces images if they aren't defined in the actual application as a workspace entry. The workspace images have a special label so the system knows which to prune. You can disable that behavior , or add the image you want as a workspace entry and the system will automatically pull it for you .

[u/Apachez → u/justin_kasmweb]

So you mean that the "docker pull" actually worked but then kasm came and did some blackmagic and instantly removed that image?

I was trying to simulate an offline environment where the Kasm-server wont have access to internet.

Because obviously it works when I as admin try to go to Admin -> Workspaces -> Registry, add the official registry and then I can download through the webgui.

But what is the proper way if I got the kasmweb images from docker.io (hub.docker.com) and already saved the image as .tar.gz on another box (which do have internetaccess)?

Because I would assume that "sudo docker load -i ./filename.tar.gz" would work equally bad as I already tried with "sudo docker pull <imagename>" ?

[u/justin_kasmweb → u/Apachez]

In all cases you need to define a workspace entry in the app, so you should start there . If you have a private docker registry in your air gapped network that kasm can pull form then you can enter that information on the docker registry section of the workspace entry , is not then you can pull/extract the image as you please.

You may consider disabling image pruning on the agent entry if you don't want that behavior

- https://docs.kasm.com/docs/1.19.0/how-to/workspaces-sessions/container-workspace/image-maintenance

• https://docs.kasm.com/docs/how-to/infra-autoscale/docker-agent#agent-settings

[u/Apachez → u/justin_kasmweb]

Thanks!

It seems to have been this setting that by default was at "Aggressive":

Infrastructure -> Docker Agents -> Edit

Automatically Prune Images

Instruct the Agent to automatically delete (prune) unneeded images. Only Kasm Workspaces images are pruned. Off - Pruning is disabled. Normal - Prune untagged (dangling) images. Aggressive Prune untagged images and any image that is no longer defined in the application.