-
-
Notifications
You must be signed in to change notification settings - Fork 33
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] Kasm Wizard hangs and does not install the selected packages (unRAID 6.12.13) #74
Comments
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid. |
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. |
I am experiencing a similar issue, clean install, docker folder dedicated to a SSD. Installation output ends with a complete, but then brings me to this weird dashboard where there's a button at the bottom to "Stop the install wizard" as if it never finished. When I access the login screen via the https port, no password I set works and when I tried resetting it as instructed in the admin reset instructions, the default "password" still doesn't work. |
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. |
This issue is locked due to inactivity |
Is there an existing issue for this?
Current Behavior
Kasm Wizard does not progress and shows a blank terminal screen no matter how long I wait. This appears selecting which applications I want installed on the preceding page. Refreshing the page returns me back to the beginning of the wizard where I'm prompted to agree to the terms and conditions.
Expected Behavior
Selected applications should be installed and the user can confirm this is progressing as expected by seeing a bunch of text appear on the black terminal screen as the selected applications are downloaded and installed.
Steps To Reproduce
Oct 8 16:08:11 Ares kernel: docker0: port 1(veth8d207d9) entered blocking state
Oct 8 16:08:11 Ares kernel: docker0: port 1(veth8d207d9) entered disabled state
Oct 8 16:08:11 Ares kernel: device veth8d207d9 entered promiscuous mode
Oct 8 16:08:12 Ares kernel: eth0: renamed from vethd8a3948
Oct 8 16:08:12 Ares kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth8d207d9: link becomes ready
Oct 8 16:08:12 Ares kernel: docker0: port 1(veth8d207d9) entered blocking state
Oct 8 16:08:12 Ares kernel: docker0: port 1(veth8d207d9) entered forwarding state
A quick Google search of some of the common terms above suggests that there may be other Docker installs using the same ports. This is not the case on my machine. unRAID does a good job at identifying if a port is being used by another container when you first install a new application. I didn't get this warning and manually checking all my Docker containers confirmed there are no issues of shared port usage.
Since removing the Kasm Docker container, I no longer see the error above in my unRAID logs.
Environment
CPU architecture
x86-64
Docker creation
Screen shot provided in earlier section.
Container logs
The text was updated successfully, but these errors were encountered: