KasmVNC
gluetun
Our great sponsors
KasmVNC | gluetun | |
---|---|---|
46 | 374 | |
2,189 | 5,867 | |
7.1% | - | |
7.9 | 9.1 | |
14 days ago | 7 days ago | |
C++ | Go | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
KasmVNC
-
Orb is a free and open source web desktop
Not exactly the same thing, but I had good experience with KasmVNC.
Despite having VNC in its name, it isn't fully compliant with the VNC protocol and doesn't support regular VNC clients. Instead, it exposes a web client that you can access to connect to the machine. It also felt surprisingly snappy and nice to use compared to my previous experiences with regular VNC.
-
Please clarify the licensing of Kasm
- KasmVNC is a standalone open source project that powers the container steaming portion of workspaces - meaning the rendering of the container GUI environment and the keyboard/mouse interaction. KasmVNC can be used in containers, VMs or hardware. It is GPL2. https://github.com/kasmtech/KasmVNC
-
Kasm has been busy
The rendering for container sessions is powered by our independent open-source project KasmVNC . Here is a video on some of the improvements to the streaming tech we've made in recent months. It shows an example of how performant it can be
-
Self-Hosted Containerized VDI: Gui Desktop and Application Containers Launched On-Demand and Delivered to Your Browser + Remote access to anything else with SSH/VNC/RDP via Kasm Workspaces - New Release 1.13: 3rd Party Registries / Session Snapshots / AMD & Integrated graphics acceleration
- https://github.com/kasmtech/KasmVNC
Our bread and butter is container streaming, which allows you to instantly provision Linux desktop environments and Gui applications. But we also support remote access to any other machine you may have that are running our open-source project KasmVNC, or SSH, RDP, and traditional VNC.
-
Desktop Sharing to work from another computer
I'm running Kasmvnc (https://github.com/kasmtech/KasmVNC) on KDE-Neon at the moment.
- What part is open source ?
-
Would it be possible to have a MacOS container?
Kasm expects that it's container images are running KasmVNC . You can see that's one of the steps when we build the "core" images which all of the other images are based on. I see that Docker-OSX can support running a VNC server, but that would need to be swapped with KasmVNC . Without digging in, I'm not sure what the level of effort would be. At glance I can see there are tricks with X11/Display, and its not immediately clear what the interplay is with kvm's vnc capabilities if any.
-
Port 19302 and 3478
All of the Workspaces Images (e.g Chrome , CentOS) utilize KasmVNC for the browser based rendering of the container. In the latest version for KasmVNC we added the underpinnings for WebRTC UDP transport. Its not fully plumbed into the full Workspaces platform yet, but its usable in KasmVNC standalone.
-
What do I need to get sound on fixed infrastructure ?
I want KasmVNC + working sound connecting to a fixed infrastructure. What do I need to set this up ? according to this issue https://github.com/kasmtech/KasmVNC/issues/31 , it's available in the commercial kasm server. That's fine and I'm OK to pay for a license, but how does the sound setup work ? I don't see a mention of sound here: https://www.kasmweb.com/docs/latest/how_to.html
gluetun
-
It's this time of the year again... which open-source project are you donating to?
The last couple of years I have been donating to Gluetun.
-
How to host a docker based proxy for selected containers
One option I could find is Gluetun, which looks very popular and actively maintained. In this case we have one single point of contact with VPN provider. The other containers should be run with network_mode: service:gluetun. If I understand correctly, those container will use VPN for every network operation, even for inter-container communication. Would they be visible for the containers not attached to gluetun (e.g. the SWAG reverse proxy)?
-
running a docker with a torrent client and vpn INSIDE the container... bad idea?
I setup Gluetun with qbittorrent in docker. Gluetun connects to the nord via manual login and I get to choose the specific servers I want it to you in its environment variables.
I use gluetun https://github.com/qdm12/gluetun supports multiple vpn providers
-
NordVPN - AUTH_FAILED Your credentials might be wrong
# See https://github.com/qdm12/gluetun/wiki
-
Routing torrenting on a home server through VPN
Have you ever heard about gluetun? I think it could be a good solution, or at least this is what Iām using and liking it so far to route my torrent client downloads
-
Recent terrible streaming services price and shows being butchered left and right pushed me to start building my own self-hosted media server. Using Plex as its easiest to setup sharing with families and friends with the *arr suite running via docker with [Ezarr](https://github.com/Luctia/ezarr)
Gluetun - Creates the VPN connection
Not sure of a free one. I use NordVPN with this docker container https://github.com/qdm12/gluetun and it works great.
-
Is ProtonVPN committed to offering port forwarding?
It's a bit complex but I use a setup of three docker containers which all share the same networking. I use Gluetun (https://github.com/qdm12/gluetun) as the VPN client and qbittorrent as the torrent client (I use the linuxserver io image but any should qbittorrent client should work). For the port forwarding I use https://github.com/soxfor/qbittorrent-natmap which uses nat-pmp to request a port from ProtonVPN via the Gluetun interface and then automatically updates it in qbittorrent. Gluetun apparently supports Proton port forwarding by default and exposes the port via its API if you want to write your own script, but I couldn't get it to work and it uses openvpn. This setup uses a wireguard config on gluetun from Proton with nat-pmp enabled. I run this on a random weak decade old computer 24/7 but in a desktop environment you should be able to just run it on Docker desktop when you want to torrent. The docker compose file in the natmap repo gives a good idea of this docker stack.
-
New to go, suggestions for non-web projects.
There is https://github.com/vishvananda/netlink which deals with low level networking stuff, maybe helping out there would be nice. I use it for https://github.com/qdm12/gluetun (also in Go)
What are some alternatives?
docker-wireguard-pia - A Docker container for using Wireguard with PIA.
openvpn-client
docker-transmission-openvpn - Docker container running Transmission torrent client with WebUI over an OpenVPN tunnel
docker-desktop - A Dockerized light-weight desktop environment accessible from the browser with NoVNC. Firefox Browser included.
nordlynx
nordvpn - NordVpn Docker Client
docker-qBittorrentvpn - Docker container which runs a headless qBittorrent client with WebUI and optional OpenVPN
htpc-download-box - Sonarr / Radarr / Jackett / NZBGet / Deluge / OpenVPN / Plex
synology-wireguard - WireGuard support for some Synology NAS drives
docker-windscribe-socks-server - Containerizes a SOCKS5 proxy server with traffic tunneled through Windscribe's VPN service
arch-delugevpn - Docker build script for Arch Linux base with Deluge, Privoxy and OpenVPN
docker-openvpn - š OpenVPN server in a Docker container complete with an EasyRSA PKI CA