How to Remove kasm_share Container

When Kasm is deployed with a remote database and no Redis server is provided, the kasm_share container will continuously check for a connection to a Redis server. The logs will show messages similar to:

Unable to initialize redis connection.... Connection timed out.

The kasm_share container is only necessary for the shared session chat feature and without a Redis server this container should be removed.

 Instructions

1. Stop the Kasm services on the Kasm Manager VM

   sudo /opt/kasm/bin/stop

2. Comment out or delete the kasm_share section of docker-compose.yaml

   sudo nano /opt/kasm/current/docker/docker-compose.yaml
   # kasm_share: # container_name: kasm_share # user: root # image: "kasmweb/share:1.16.1" # networks: # - kasm_default_network # volumes: # - /opt/kasm/1.16.1:/opt/kasm/current # restart: always # logging: # driver: "json-file" # options: # max-size: "10m" # max-file: "20"

3. Comment out the contents of, or delete upstream_share.conf

   sudo nano /opt/kasm/current/conf/nginx/upstream_share.conf
   # upstream kasm_share { # server kasm_share:8182; # }

4. Comment out the contents of, or delete share_api.conf

   sudo nano /opt/kasm/current/conf/nginx/services.d/share_api.conf
   # location /api/share/ { # proxy_http_version 1.1; # proxy_set_header Host $host; # proxy_set_header Upgrade $http_upgrade; # proxy_set_header Connection "upgrade"; # proxy_set_header X-Real-IP $remote_addr; # proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; # proxy_set_header X-Forwarded-Proto $scheme; # # add_header Strict-Transport-Security "max-age=63072000" always; # # proxy_pass http://kasm_share; # }

5. Restart Kasm services on the Kasm Manager VM

   sudo /opt/kasm/bin/start

Related Docs:

• Standalone Remote Database

• Redis