-
-
Notifications
You must be signed in to change notification settings - Fork 41
[BUG] Container not starting after system reboot #75
Copy link
Copy link
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Every time I reboot my computer I need to uninstall linoffice, reboot again, and then re-install linoffice. The issue stems from podman:
Error: OCI runtime error: unable to start container "24022c73018352e917b36a06abadbc9208f7143ca98af0191f3a29e5f5d138bb": runc: runc create failed: unable to start container process: error during container init: unable to join session keyring: unable to create session key: disk quota exceeded
I have 161GB free storage on the device. If I just re-install without rebooting I get "storage driver issue" and the log file isn't created so I can't look. I think having a -v option for verbose output in the GUI would be really helpful.
To Reproduce
Installed latest release (2.0.0), rebooted my system, and couldn't open office apps again because the container just didn't start.
System information
- LinOffice version: 2.0.0
- Linux distribution: Kali 6.16.8-1kali1 (2025-09-24) x86_64
- Desktop environment: X11
- How did you install Podman-Compose (e.g. from repo or via pip): repo
- How did you install FreeRDP (e.g. from repo or as Flatpak): repo
Additional notes
When I had dockurr/windows installed on docker I had no problem restarting it. Maybe giving a docker install option would be a good idea.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working