Container workloads silently failing (errors only shown in logs)

At first the Salad app showed errors, and after adjusting my software firewall those went away. Now I’m not getting any error notifications, but the logs have errors showing that container workloads are failing. I’ve been offered container workloads many times, and every time one tries to start it fails.

I pored over all the Troubleshooting guides on the Salad site, and have done everything I can think of.

For example:

- I have both CPU and GPU enabled.
- I have the latest version of Salad, 1.4.7.
- I’ve used Powershell as Admin with the command “wsl --update” to update WSL to the latest.
- Virtualization is enabled in my BIOS.
- I’m not using a VPN.
- I have over 50 GB of free space available on drive C.

Even submitted logs to Salad support a few days ago. They said they would get back to me, but it’s been multiple days and I’m not sure they’ll ever follow up. In the meantime I’m missing out on the more profitable container workloads.

I’m trying to determine if the errors are on my side of things and I can do something about it, or at Salad’s end.

It’s probably for naught, but I thought I’d try posting here and seeing if perhaps anyone had an idea of what’s going on in my case. To me, it looks like something is wrong on Salad’s end, but I’m just not sure.

If it helps: I have a Ryzen 3700X CPU, 16 GB, RTX 3060 12 GB. Which I know isn’t amazing, but it would meet the minimum requirements.

These are the kinds of errors I’ve been seeing in my logs. (I’ve censored certain parts with XXXXX.)

[WRN] Failed to retrieve process with PID XXXXX

[INF] Call failed with gRPC error status. Status code: '"Unavailable"', Message: 'Error connecting to subchannel.'.
System.Net.Sockets.SocketException (11001): No such host is known.

[INF] Call failed with gRPC error status. Status code: '"Unavailable"', Message: 'Error connecting to subchannel.'.
System.Net.Sockets.SocketException (10061): No connection could be made because the target machine actively refused it.

[INF] Call failed with gRPC error status. Status code: '"Unavailable"', Message: 'Error reading next message. IOException: The request was aborted. IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.. SocketException: An existing connection was forcibly closed by the remote host.'.
System.IO.IOException: The request was aborted.

[INF] Call failed with gRPC error status. Status code: '"NotFound"', Message: 'failed to resolve reference "XXXXX:latest": failed to do request: Head "XXXXX/manifests/latest": dial tcp: lookup XXXXX on XXXXX:53: read udp XXXXX:36810->XXXXX:53: i/o timeout'.

[ERR] SpinnerContainerContext: Failed to pull image
Grpc.Core.RpcException: Status(StatusCode="NotFound", Detail="failed to resolve reference "XXXXX:latest": failed to do request: Head "XXXXX/manifests/latest": dial tcp: lookup XXXXX on XXXXX:53: read udp XXXXX:36810->XXXXX:53: i/o timeout")

[WRN] Install Status: InstallFailure(IMAGE_PULL - XXXXX:latest, @20:29:05 XXXXX:latest pull failed)

[INF] Call failed with gRPC error status. Status code: '"Unavailable"', Message: 'Error starting gRPC call. HttpRequestException: An error occurred while sending the request. IOException: The request was aborted. IOException: The response ended prematurely while waiting for the next frame from the server.'.

[INF] Call failed with gRPC error status. Status code: '"Unavailable"', Message: 'Error starting gRPC call. HttpRequestException: An error occurred while sending the request. IOException: The request was aborted. IOException: An HTTP/2 connection could not be established because the server did not complete the HTTP/2 handshake. IOException: The response ended prematurely while waiting for the next frame from the server.'.
System.Net.Http.HttpRequestException: An error occurred while sending the request.

[INF] Call failed with gRPC error status. Status code: '"Internal"', Message: 'Error reading next message. HttpProtocolException: The HTTP/2 server reset the stream. HTTP/2 error code 'INTERNAL_ERROR' (0x2).'.

Hi, as there is no error within the app and is only in the logs you will have to wait for offical support to get back to you, some things are just not known inside the community (this being one of them) and some things are just bugs on salads end meaning we are unable to fix them, your best bet is to wait for a response from salad and they will get back to you when there is a fix to the issue what may take a tiny bit of time.

I have a similar setup except with 32gb of ram. Every week i get the “you are a star chef” notification but it never shows on the ui, i haven’t had a container job in 2 days now and for a few days prior i would get a job for like 10 minutes then they would stop. With me not even touching the computer. idk what is going on but salad just doesn’t seem to work on by PC anymore. I wouldn’t be surprised if I’m also getting these errors.

I have the same problems, most likely after the update to 1.4.7, I wrote to support a month ago, they wrote that they will write when they find out the cause, still no answer. Before that everything worked perfectly, I wonder what broke that they do not fix for a month, or it is difficult to fix, or there are few people like us and it is not worth attention.

What does the Unable to run a container workload Error-1 means it comes almost daily and after retrying for few mins and waiting it resolves automatically. But if I am not there it would waste a lot of my time. Simultaneously when this issue appears the GPU utilisation remains 100% and when I click retry gpu utilisation drops to zero then after few attempts everything remains normal. While on status there degraded written.

I got the same problem is there any fix??

Thank you for the reply, appreciate it. I guess I’ll keep waiting for Salad’s support to get back to me.

But perhaps others will see this, and can share whether or not the same is happening to them, if they check their logs. That it might not be that people aren’t receiving container workloads, but rather they’re failing. And it’s why their earnings haven’t been great recently. If this problem is widespread. I don’t know. It might just be my location, my specific setup . . . I honestly don’t know for sure.

Yeah, I’m starting to wonder if many of the complaints about not receiving container workloads are actually cases where people are getting containers, but they’re failing to run.

I noticed my CPU and GPU loads dropping to 0% in preparation for a container workload many times, but then Salad almost immediately went back to mining. Which is what got me to check my logs. Sure enough, it was the fact that the workloads were failing to run. Best guess is the problem is at Salad’s servers, but I honestly don’t know for certain.