raw plover
Greetings!. I am stuck at chopping power 3/4 where the 4th step is to setup WSL. I keep landing on this page everytime I click on setup container environment. However clicking the setup wsl does not seem to do anything. I already have wsl installed (ubuntu) alongside docker which I use for my development work, but I can't seem to move ahead. I tried the wsl update command several times, rebooted my pc several time, still no luck. Any help is much appreciated. Thanks!
grave egret
im no expert but i would suggest maybe try to export your ubuntu to a backup file, remove wsl let salad install it and then bring back the ubuntu with the backup you made
halcyon pewter
Salad has a hard time installing it's container environment when you already have other VML install such as Ubuntu and other dockers.
As Johnny suggested, try uninstall all other Linux based programs and just have Salad install. That should allow it to install with no issue.
short kestrel
Greetings!. I am stuck at chopping power 3/4 where the 4th step is to setup WSL....
try running bcdedit /set hypervisorlaunchtype auto in cmd as an admin and restart your machine
the issue isn't that wsl is misconfigured, windows isn't reporting to salad that virtualisation is properly enabled
raw plover
Hello. I happened to randomly get a notification saying I am eligible for container workload or something similar and the next moment I notice the setup container environment was checked. I will keep this command handy next time i face the issue. Thanks!
Oddly, I do notice a pattern. I am using remote desktop client to connect to my PC remoteltly. Until recently I was using the windows official rdp which is where I could not setup the container and also I kept facing salad is degraded and it kept trying to connect (even though I was able to earn rewards for the jobs). This used to only happen after I start chopping. Today, I switched to parsec for remote desktop and salad seems to work absolutely fine. The container is setup and I don't see the degradation and reconnection attempts. To verify, I switched back to windows rdp and the issue was back on. I switched around 5 times and everytime I was on windows rdp, salad had some issues. parsec/chrome's rdp seems to not cause any issues.
Perhaps something the devs could take a look at or is this an expected behaviour?
short kestrel
ah yes, RDP protocol based applications do not work with Salad
we say we don't support remote applications if installed at all, but really as long as you're not using one based on RDP it should work fine
most notably Chrome Remote Desktop since we can't provide support for Parsec users due to the virtualisation Parsec uses
however that being said if you were to contact official support with a strange issue and we notice any virtual devices we won't be able to provide support due to the vast causes of different virtual drivers