search

linuxserver / docker-kasm

Kasm Workspaces platform provides enterprise-class orchestration, data loss prevention, and web streaming technology to enable the delivery of containerized workloads to your browser.
GNU General Public License v3.0
271 stars 27 forks source link

[BUG] server.py lin 178 #60

Open patpac9 opened 1 month ago

patpac9 commented 1 month ago

Is there an existing issue for this?

Current Behavior

won't install correctly because file "/opt/kasm/current/conf/app/api.app.config.yaml" does not exist.

ls in "/opt/kasm/" looks like this: Folder: 1.15.0 Folder: certs

There is no "current" folder. ("/opt/kasm/current/conf/app/api.app.config.yaml") I tried to copy the folder "1.15.0" to "current" but I still get the same error message.

Expected Behavior

find /opt/kasm/current/conf/app/api.app.config.yaml

Steps To Reproduce

  1. Install this container on TrueNAS via custom app UI based on the info from "Docker creation"
  2. Connect to the website and add the credentials for admin and user.
  3. select any kasm workspace
  4. in the installation screen the error shows up

Environment

- OS: TrueNAS Scale Dragonfish-24.04.1.1
- How docker service was installed: was already installed

CPU architecture

x86-64

Docker creation

docker run -d \
  --name=kasm \
  --privileged \
  -e KASM_PORT=443 \
  -p 3000:3000 \
  -p 443:443 \
  -v mnt/Data/kasm/data:/opt \
  -v mnt/Data/kasm/profiles:/profiles
  lscr.io/linuxserver/kasm:latest

Container logs

((Install script on website))
...
4ed3079644a9 Pull complete 
kasm_api Pulled 
Traceback (most recent call last):
  File "server.py", line 178, in <module>
Exception: Unable to find config /opt/kasm/current/conf/app/api.app.config.yaml
[1] Failed to execute script 'server' due to unhandled exception!
github-actions[bot] commented 1 month ago

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

LinuxServer-CI commented 2 weeks ago

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.