Closed cinderblockgames closed 1 year ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
I cannot replicate this, what is your underlying storage driver? I am testing on overlay2.
-rw-rw-r-- default_images_amd64.yaml
-rw-rw-r-- default_images_arm64.yaml
I've got it bind mounted to a NAS. I can try having /opt
mounted to the local fs; if I keep the /profiles
on the NAS, is that all I need for a backup of the user space?
This is a DinD container that spins up an isolated docker environment. It needs a real disk for /opt. You can just try not mounting anything on opt and use a docker volume. That should fall back to fuse-overlayfs and it would let you know if it at least functions and that's your issue.
Okay, I used local fs for /opt
and it installed and I can now get to the :443
UI. I should be able to log in with the user@kasm.local
or admin@kasm.local
accounts, right?
Yes it will be the passwords you entered in the wizard.
I get login failed, but I wonder if it's because it can't register the service worker because of the self-signed cert.
Is there a way to disable SSL in the container so I can have traefik in front of it? If I use traefik in front of 3000, I get a Bad Gateway, and, if I use it in front of 443, I get 400 Bad Request: The plain HTTP request was sent to HTTPS port
.
Okay, I need to specify for traefik to connect to the container using https:
- 'traefik.http.services.kasm.loadbalancer.server.scheme=https'
- 'traefik.http.services.kasm-install.loadbalancer.server.scheme=https'
I also needed to allow invalid certs in the traefik config:
[serversTransport]
insecureSkipVerify = true
I think it would be better to be able to turn off TLS inside the container altogether, but the above works to serve the container as it is, at least.
However, I still can't log in.
I'll close this issue, though, since it's been resolved by having /opt
locally.
Thanks!
Is there an existing issue for this?
Current Behavior
Once I get to the install piece, I get a permission denied error:
When I check the permissions on the files under
seed_data
, I saw that they didn't have any write permissions:So, I added those:
And ended up with:
However, when I start the install again, I hit the same error, and it looks like the installer is stripping the write permissions (I'm assuming by copying files that don't have write permissions):
Expected Behavior
Should be able to install.
Steps To Reproduce
Environment
CPU architecture
x86-64
Docker creation
Container logs