need to enable plugin manually every time -plugin kasmweb/sidecar:1.1 found but disabled

[DevLenn]

Hi,

I successfully installed Kasm via the installer .sh script on a Debian system about two months ago. Now, I'm trying to install it on another Ubuntu machine using the same method I used on the Debian system. After the initial installation, everything works as expected. However, after a EVERY reboot, the kasm_proxy container fails to start, and I receive the following error message:

Error response from daemon: failed to add endpoint: plugin kasmweb/sidecar:1.1 found but disabled Error: failed to start containers: kasm_proxy

Currently, whenever I want to use Kasm, I need to manually enable the plugin. Is there any way to enable this plugin permanently?

Thank you, Lenn

[DevLenn]

This worked for me:

master@pcname:~$ sudo docker network disconnect kasm_sidecar_network <container>
master@pcname:~$ sudo docker network connect bridge <container>
master@pcname:~$ sudo docker start <container>

Would not recommend, probably not healthy...

[unclesp1d3r]

Has anyone ever discovered a more reasonable solution to this problem? I’m experiencing the same exact issue.

[j-travis]

When reporting issues, can you please provide the requested information. It helps us orient to your environment to begin troubleshooting. Without it , the community has little to go on. Understanding how you installed , the distro , docker configuration etc are just a few of the basic items we need. You'll see this list when you try and open a ticket:

https://github.com/kasmtech/workspaces-issues/issues/new?template=bug_report.md

[tustunkok]

This is exactly the same error I am encountering with. Still no solution.

[nigel-dev]

Also just ran into this issue. A reboot caused the proxy to not start up like it should have. Reading through some threads others have had some success doing a fresh install with the following flags sudo bash kasm_release/install.sh -e --skip-egress

I already had a fully configured system with SSO, users and servers, so I really did not want to have to do a fresh install to fix this issue, so I did an upgrade with the same --skip-egress flag, but to my horror when it came back up it was a fresh install! None of the configs in place, none of the same users, etc. I made use of the automated upgrade script as well.

The upgrade process took a db backup but when I restored that backup it brought my users and SSO settings back to life, but none of the workspaces would launch. I removed and installed the same ones and they are still failing to launch for who knows what reason.

So now it looks like i really do get to do the fresh install route.... reconfigure SSO....servers.....agents..... 😡

[thijsk]

I just had the same experience, services wouldn't start after reboot. Update wiped all configuration.

[j-travis]

@tustunkok , @nigel-dev , @thijsk , @unclesp1d3r , @DevLenn If you are experiencing this issue, please provide the requested information about your environment here: https://github.com/kasmtech/workspaces-issues/issues/new?template=bug_report.md

[NockerMx]

This worked for me: docker plugin ls find kasmweb/sidecar:1.1, it's maked as disabled docker plugin enable kasmweb/sidecar:1.1 and finally restart Kasm sudo /opt/kasm/bin/stop sudo /opt/kasm/bin/start

[Iucasmaia]

This worked for me: docker plugin ls find kasmweb/sidecar:1.1, it's maked as disabled docker plugin enable kasmweb/sidecar:1.1 and finally restart Kasm sudo /opt/kasm/bin/stop sudo /opt/kasm/bin/start

Thanks, this worked!

[wingcomm]

Still seeing this here in September. @NockerMx 's suggestion worked but I swapped in 1.2 for 1.1.

[j0nny55555]

Using 1.7 and seeing this with some frequency and it might seem generally after a reboot

For a while I would try to use restart - and then reboot the host, but it seems there are a few docker commands (and I had to add my user to the docker group) and then stop and start, and that might just work for now