Open apiziali opened 1 year ago
The signal image is build on the ubuntu focal (20.04) base (https://github.com/kasmtech/workspaces-images/blob/develop/dockerfile-kasm-signal#L2) But, remember containers still use the kernel from your host.
So, my guess is that Signal is detecting the old kernel from 18.04 and giving you this warning since ubuntu 18.04 reached end of standard support last month.
Existing Resources
Describe the bug I installed Kasm Workspaces Community Edition on my Ubuntu 18.04 workstation, followed by the Signal Desktop image. When I run Signal in my user workspace, it displays the message: "Signal desktop will no longer support your computer's version of Linux soon. To keep using Signal, update your computer's operating system by Sep 4, 2023. Learn more."
Why isn't this workspace presenting a supported version of Ubuntu (20.04 or 22.04) to Signal Desktop?
To Reproduce Steps to reproduce the behavior:
Expected behavior Signal Desktop should not complain the OS it is running on its air to expire.
Screenshots If applicable, add screenshots to help explain your problem.
Workspaces Version Version 1.13.1.421524
Workspaces Installation Method Single Server.
Client Browser (please complete the following information):
Workspace Server Information (please provide the output of the following commands):
uname -a
: Linux elijah 5.4.0-153-generic #170~18.04.1-Ubuntu SMP Thu Jun 22 16:07:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linuxcat /etc/os-release
: NAME="Ubuntu" VERSION="18.04.6 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.6 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" VERSION_CODENAME=bionic UBUNTU_CODENAME=bionicsudo docker info
: Client: Context: default Debug Mode: false Plugins: compose: Docker Compose (Docker Inc., v2.5.0)Server: Containers: 11 Running: 8 Paused: 0 Stopped: 3 Images: 15 Server Version: 20.10.21 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Native Overlay Diff: true userxattr: false Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 1 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc Default Runtime: runc Init Binary: docker-init containerd version: runc version: init version: Security Options: apparmor seccomp Profile: default Kernel Version: 5.4.0-153-generic Operating System: Ubuntu 18.04.6 LTS OSType: linux Architecture: x86_64 CPUs: 6 Total Memory: 31.18GiB Name: elijah ID: PYR4:LNP2:DKVM:4G5A:4YR7:34PC:AULG:BTEZ:CGD5:5YY4:THXC:BRNK Docker Root Dir: /var/lib/docker Debug Mode: false Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false
WARNING: No swap limit support
sudo docker ps | grep kasm
Additional context Add any other context about the problem here.