search

kasmtech / workspaces-issues

19 stars 4 forks source link

[Bug] - Can not resume containers once they are paused. #624

Open bruman opened 1 month ago

bruman commented 1 month ago

Existing Resources

Describe the bug KASM workspaces are unable to start after a period of time

To Reproduce Steps to reproduce the behavior:

  1. happens with multiple workspaces, Jammy, and Kali linux.
  2. start the session, come back the next day or so, click on resume,
  3. Fails to start with the error message kasm not running.
  4. When i look at the docker container i see 
0bb1a9928825   kasmweb/kali-rolling-desktop:1.15.0           "/dockerstartup/kasm…"   7 days ago     Up 9 minutes (Paused)   4901/tcp, 5901/tcp, 6901/tcp                                                   ian_718a5e36

What appears to be happing the container is paused. I have tried manually unpausing, and I can then get into the host with 

sudo docker exec -it ian_718a5e36 /bin/bash

but when i connect via the web UI it pauses again.

Idle_disconnect is 60 session_time_limt is 0 allow_kasm_pause enabled allow_kasm_stop enabled keepalive_expiration = 3600 keepalive_expiration_action = pause.

Expected behavior I should be able to restart a container and connect.

Screenshots If applicable, add screenshots to help explain your problem.

Workspaces Version 1.15.0.577587

Workspaces Installation Method Single Server

Client Browser (please complete the following information): Chrome 128

Workspace Server Information (please provide the output of the following commands):

Server: Containers: 48 Running: 23 Paused: 1 Stopped: 24 Images: 124 Server Version: 27.1.1 Storage Driver: overlay2 Backing Filesystem: xfs Supports d_type: true Using metacopy: false Native Overlay Diff: true userxattr: false Logging Driver: json-file Cgroup Driver: systemd Cgroup Version: 2 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog Swarm: inactive Runtimes: runc io.containerd.runc.v2 Default Runtime: runc Init Binary: docker-init containerd version: 2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41 runc version: v1.1.13-0-g58aa920 init version: de40ad0 Security Options: seccomp Profile: builtin cgroupns Kernel Version: 5.14.0-427.28.1.el9_4.x86_64 Operating System: Rocky Linux 9.4 (Blue Onyx) OSType: linux Architecture: x86_64 CPUs: 24 Total Memory: 62.32GiB Name: aberdeen.iwasdot.com ID: e9748166-8f74-4bff-90d0-fbb07002e75f Docker Root Dir: /mnt/docker Debug Mode: false Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false

b4c51cedba6a kasmweb/ubuntu-jammy-desktop:1.15.0-rolling "/dockerstartup/kasm…" 3 hours ago Up 3 hours 4901/tcp, 5901/tcp, 6901/tcp ian_af308252 0bb1a9928825 kasmweb/kali-rolling-desktop:1.15.0 "/dockerstartup/kasm…" 7 days ago Up 19 minutes (Paused) 4901/tcp, 5901/tcp, 6901/tcp ian_718a5e36 a3ee77cfadc0 kasmweb/nginx:1.25.3 "/docker-entrypoint.…" 2 months ago Up 3 hours 80/tcp, 0.0.0.0:4443->4443/tcp, :::4443->4443/tcp kasm_proxy cb6700cd1645 kasmweb/agent:1.15.0 "/bin/sh -c '/usr/bi…" 2 months ago Up 3 hours (healthy) 4444/tcp kasm_agent c0e2f45940e1 kasmweb/share:1.15.0 "/bin/sh -c '/usr/bi…" 2 months ago Up 3 hours (healthy) 8182/tcp kasm_share 43ecbb2282ae kasmweb/manager:1.15.0 "/bin/sh -c '/usr/bi…" 2 months ago Up 3 hours (healthy) 8181/tcp kasm_manager 58630e7102c0 kasmweb/api:1.15.0 "/bin/sh -c '/usr/bi…" 2 months ago Up 3 hours (healthy) 8080/tcp kasm_api 0f30594e8c67 postgres:12-alpine "docker-entrypoint.s…" 2 months ago Up 3 hours (healthy) 5432/tcp kasm_db 89a8c76b4de4 redis:5-alpine "docker-entrypoint.s…" 2 months ago Up 3 hours 6379/tcp kasm_redis ada6b9836076 kasmweb/kasm-guac:1.15.0 "/dockerentrypoint.sh" 2 months ago Up 3 hours (healthy) kasm_guac Additional context

lostwindsenril commented 1 week ago

I have the same issue.