Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S SWC
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ExaCT
  • SWC
  • Issues
  • #2

Closed
Open
Created Jan 14, 2022 by Stefano Alberto Russo@stefano.russoOwner

The X11Web container uses a KasmVNC which does not support dynamic socket allocation

The KasmVNC container tries to use a custom KasmVNC build with support for dynamic socket allocation, but it has a bug in handling websockets.

For this reason, the container rollback using the Xkasmvnc binary from a KasmVNC version which does not support dynamic socket allocation.

  • TODO: build KasmVNC "latest" with the support for dynamic socket allocation and ensure that the build has the websocket bug fixed.
Assignee
Assign to
Time tracking