kasmtech
[Bug] - Disk Space Consumption Increases by ~1GB with Each Stop/Resume Cycle
Description:
I'm running Kasm Workspaces version 1.16.1 (latest release) and have encountered a recurring issue with disk space usage. Every time I stop an instance (without deleting it) and then resume it, I notice that the available disk space decreases by approximately 1GB. Repeating this cycle consistently consumes additional disk space (~1GB per cycle), which eventually leads to significant disk space loss.
Steps to Reproduce:
- Start an instance in Kasm Workspaces.
- Stop the instance (do not delete it).
- Resume the same instance.
- Observe that the disk space on the host system decreases by around 1GB.
- Repeat the process to see the cumulative effect.
Expected Behavior:
Stopping and resuming an instance should not continually consume additional disk space. Once an instance is stopped, any temporary data or snapshots should be properly cleaned up or merged without leaving residual data.
Actual Behavior:
With every stop/resume cycle, about 1GB of disk space is being used, suggesting that some temporary files, logs, or snapshot/diff layers are not being cleaned up as expected.
Additional Information:
- I have verified this behavior multiple times and have not found any similar issues reported in the community or in the GitHub issues for Kasm Workspaces.
- It appears that the system might be accumulating data (possibly related to container diff layers or temporary snapshots) that is not reclaimed after resuming the instance.
Questions:
- What is causing this disk space consumption during the stop/resume process?
- Is there a configuration setting or cleanup mechanism that I may have missed?
- Are there any plans for a fix or workaround in an upcoming release?
I appreciate any help or insight you can provide regarding this issue. Thank you!
Thank you for reporting. When opening a new ticket, we ask a handful of questions to provide info about your operating environment. It provides a starting point for the community to understand and potentially identify/ replicate the issue. Without it we have little to go on. Please add the requested information you see here: https://github.com/kasmtech/workspaces-issues/issues/new?template=bug_report.md
Thank you for reporting. When opening a new ticket, we ask a handful of questions to provide info about your operating environment. It provides a starting point for the community to understand and potentially identify/ replicate the issue. Without it we have little to go on. Please add the requested information you see here: https://github.com/kasmtech/workspaces-issues/issues/new?template=bug_report.md
Description:
I'm running Kasm Workspaces version 1.16.1 (latest release) and have encountered a recurring issue with disk space usage. Every time I stop an instance (without deleting it) and then resume it, I notice that the available disk space decreases by approximately 1GB. Repeating this cycle consistently consumes additional disk space (~1GB per cycle), which eventually leads to significant disk space loss.
Steps to Reproduce:
- Start an instance in Kasm Workspaces.
- Stop the instance (do not delete it).
- Resume the same instance.
- Observe that the disk space on the host system decreases by around 1GB.
- Repeat the process to see the cumulative effect.
Expected Behavior:
Stopping and resuming an instance should not continually consume additional disk space. Once an instance is stopped, any temporary data or snapshots should be properly cleaned up or merged without leaving residual data.
Actual Behavior:
With every stop/resume cycle, about 1GB of disk space is being used, suggesting that some temporary files, logs, or snapshot/diff layers are not being cleaned up as expected.
Workspaces Version Version 1.16.1
Workspaces Installation Method Single Server
Client Browser (please complete the following information):
- Browser chrome
- Version 131.0.6778.69
Workspace Server Information (please provide the output of the following commands):
-
uname -a
-
cat /etc/os-release
-
sudo docker info
-
sudo docker ps | grep kasm
Additional Information:
- I have verified this behavior multiple times and have not found any similar issues reported in the community or in the GitHub issues for Kasm Workspaces.
- It appears that the system might be accumulating data (possibly related to container diff layers or temporary snapshots) that is not reclaimed after resuming the instance.
Questions:
- What is causing this disk space consumption during the stop/resume process?
- Is there a configuration setting or cleanup mechanism that I may have missed?
- Are there any plans for a fix or workaround in an upcoming release?
I appreciate any help or insight you can provide regarding this issue. Thank you!