Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Whenever container is restarted - Kasm breaks and looses permisson with appdata #52

Open
1 task done
marlowleon opened this issue Apr 3, 2024 · 7 comments
Open
1 task done

Comments

@marlowleon
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

[BUG] Whenever container is restarted - Kasm breaks and looses permisson with appdata

I restart and get a login page but SAML does not working anymore and cannot sign in manually, if i sign in from a cached browser i can see the inside of the app but nothing loads and i cant sign out

I tried doing unraid permissions and even chmod 777 but still no change.

Expected Behavior

Restarting container and logins work, apps work

Steps To Reproduce

Install Kasm, set up, make new user, add some apps. Restart container, then everything breaks

Environment

- OS: unRaid
- How docker service was installed: Commuinity apps

CPU architecture

x86-64

Docker creation

Used the community apps

Container logs

time="2024-04-02T22:58:37.238456882-04:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/7336539ea9c5db5c7f45c82a2ca5ee6041b5e3f17088e5782b62142ddf9d550b pid=20120 runtime=io.containerd.runc.v2
time="2024-04-02T22:58:45.385948816-04:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
time="2024-04-02T22:58:45.386019193-04:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
time="2024-04-02T22:58:45.386026839-04:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
time="2024-04-02T22:58:45.386257991-04:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/f659a8fa8d6a9b5ad59e4841ffe2df9f654dc96b69ae487c1e934e5469cf3831 pid=20196 runtime=io.containerd.runc.v2
time="2024-04-02T22:59:24.045145175-04:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
time="2024-04-02T22:59:24.045221076-04:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
time="2024-04-02T22:59:24.045227848-04:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
time="2024-04-02T22:59:24.045338516-04:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/57b37a799bc1357ed2640e14874c215326dfd92d863ae1cdbbbbd0de52b7e222 pid=20363 runtime=io.containerd.runc.v2
time="2024-04-02T22:59:28.536375183-04:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
time="2024-04-02T22:59:28.536468164-04:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
time="2024-04-02T22:59:28.536474525-04:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
time="2024-04-02T22:59:28.536600057-04:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/7336539ea9c5db5c7f45c82a2ca5ee6041b5e3f17088e5782b62142ddf9d550b pid=20435 runtime=io.containerd.runc.v2
time="2024-04-02T22:59:35.546849834-04:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
time="2024-04-02T22:59:35.546915454-04:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
time="2024-04-02T22:59:35.546921500-04:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
time="2024-04-02T22:59:35.547012141-04:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/327bb7c07324d9917872522d59a3e7931905cba82c05b4ec0901b389758f14da pid=20488 runtime=io.containerd.runc.v2
time="2024-04-02T22:59:45.785813138-04:00" level=info msg="loading plugin \"io.containerd.event.v1.publisher\"..." runtime=io.containerd.runc.v2 type=io.containerd.event.v1
time="2024-04-02T22:59:45.785884711-04:00" level=info msg="loading plugin \"io.containerd.internal.v1.shutdown\"..." runtime=io.containerd.runc.v2 type=io.containerd.internal.v1
time="2024-04-02T22:59:45.785890728-04:00" level=info msg="loading plugin \"io.containerd.ttrpc.v1.task\"..." runtime=io.containerd.runc.v2 type=io.containerd.ttrpc.v1
time="2024-04-02T22:59:45.786016791-04:00" level=info msg="starting signal loop" namespace=moby path=/run/docker/containerd/daemon/io.containerd.runtime.v2.task/moby/f659a8fa8d6a9b5ad59e4841ffe2df9f654dc96b69ae487c1e934e5469cf3831 pid=20582 runtime=io.containerd.runc.v2
Copy link

github-actions bot commented Apr 3, 2024

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@maxexcloo
Copy link

Having the same issue it seems - kasm_proxy doesn't seem to be able to load kasm_nginx.crt and kasm_nginx.key

@marlowleon
Copy link
Author

Im close to just deleteing this and reporting it to unraid

@marlowleon
Copy link
Author

update?

@marlowleon marlowleon reopened this Jun 21, 2024
@mostdcoa
Copy link

mostdcoa commented Jul 2, 2024

Having the same issue with the moby namespace

@j0nnymoe
Copy link
Member

j0nnymoe commented Jul 2, 2024

@marlowleon please provide your docker run for kasm.

@LinuxServer-CI
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Issues
Development

No branches or pull requests

5 participants