Closed ne0YT closed 5 days ago
I also tried with other apps which dont have the seccomp issue and no errors in there whatsoever but the wbetop will not load correctly and only show like this:
Any reason why you'd wouldn't just use this? https://docs.linuxserver.io/images/docker-firefox/
@j0nnymoe yes.. I just wanted to try it with firefox first to see that it works. I want to use it to run different softwares in the end.
the nginx I use rn:
docker run -d --name nginx-proxy \
-p 3001:443 \
-v /opt/kasm/nginx.conf.d:/etc/nginx/conf.d \
-v /opt/kasm/ssl:/etc/nginx/ssl \
--link webtop1 --link webtop2 --link webtop3 \
nginx:latest
default.conf:
server {
listen 443 ssl;
server_name _;
ssl_certificate /etc/nginx/ssl/nginx.crt;
ssl_certificate_key /etc/nginx/ssl/nginx.key;
location /1/ {
proxy_pass http://webtop1:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
}
location /2/ {
proxy_pass http://webtop2:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
}
location /3/ {
proxy_pass http://webtop3:3000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
}
}
Only time I've seen the lastactiveat
error is when the reverse proxy has issues dealing with websockets.
Though if it's worked with the normal webtop image, it might not be that (assuming that's behind a proxy too).
I'll let someone else wade in on the issue.
@j0nnymoe yes, the webtop image is running behind the exact same config. I can switch back and forth between the self-built firefox one and the normal webtop one. -> webtop works, self-built doesn't. thx!
We swapped Alpine based images off of Firefox because it was not working properly, might be related.
it works using alpine320 instead of alpine318 :) is there a simpler way to know the latest tag than scraping from this github page?
also maybe someone has an idea why it's laggy.. I run kasm directly on my vm and get amazing performance.. while using the docker way i's quite laggy.
Updated readme.
Is there an existing issue for this?
Current Behavior
I use nginx as a reverse-proxy to have mulitple webtops availble. this also works correctly when I use the prebuilt webtops like this:
but it doesn't work when I use the tutorial to build a simple webtop with just firefox.
I see a: [519] Sandbox: seccomp sandbox violation: pid 519, tid 519, syscall 25, args 140734628765696 4096 8192 0 0 0.
which i dont have when using the prebuilt.. as you can see I already launch it with the correct parameter to circumvent this behaviour, it still occurs.
Expected Behavior
I can access 3 webtops of firefox
Steps To Reproduce
run an nginx revproxy and the script in "Docker creation"
Environment
Docker creation
Container logs