Something went wrong while trying to create provider: RequestError

[jfrantzius]

Hi,
I tried out the Developer Sandbox extension v0.0.5 in Podman Desktop 1.20.2 on Mac M1, where I have podman 5.5.2 happily running my containers.

When following the instructions linked here:

I eventually end up with a task being shown like this:

Unfortunately, after about 4 minutes, it fails like this:

With the error message "Something went wrong while trying to create provider: RequestError"

This sounds like a bug to me? Or is there something the user could do about it at this point?

[dgolovin]

Is there anything related to this error on troubleshooting logs page?

Screen.Recording.2025-07-24.at.10.52.14.AM.mov

[dgolovin]

@jfrantzius I cannot replicate on my M1. Do you have stack trace in the log?

[jeffmaury]

@jfrantzius are you behind a proxy ?

[jfrantzius]

@dgolovin @jeffmaury from the logs I can see it trying to reach the current-context k8s cluster I have in my ~/.kube/config , but which is not reachable.

I guess for user experience it would be better if the extension didn't try to talk to any other k8s cluster? I wonder why it is doing this anyway?

[jeffmaury]

@dgolovin @jeffmaury from the logs I can see it trying to reach the current-context k8s cluster I have in my ~/.kube/config , but which is not reachable.

I guess for user experience it would be better if the extension didn't try to talk to any other k8s cluster? I wonder why it is doing this anyway?

Podman Desktop is monitoring the current context from the Kube config file. Switch to Sandbox will be done after the login command has been pasted and if the set as current context option has been enabled

[jfrantzius]

I'd like to suggest that this doesn't work so well from a user experience point of view...

Is this is something that Podman does and that the Extension cannot change?

[jeffmaury]

I'd like to suggest that this doesn't work so well from a user experience point of view...

Is this is something that Podman does and that the Extension cannot change?

I don't think Podman is involved here. Is there a way to get an extract of the log when the error occurs ?

[jfrantzius]

The log is full of this, with that (anyonymized) context being my current-context in ~/kube/config

main ↪️ Trying to watch pods on the kubernetes context named "my-ns/some-ocp:port/my.username@somewhere" but got a connection refused, retrying the connection in 5s.
main ↪️ Trying to watch deployments on the kubernetes context named "my-ns/some-ocp:port/my.username@somewhere" but got a connection refused, retrying the connection in 11s.
main ↪️ Trying to watch pods on the kubernetes context named "my-ns/some-ocp:port/my.username@somewhere" but got a connection refused, retrying the connection in 6s.
main ↪️ Trying to watch pods on the kubernetes context named "my-ns/some-ocp:port/my.username@somewhere" but got a connection refused, retrying the connection in 7s.
main ↪️ Trying to watch deployments on the kubernetes context named "my-ns/some-ocp:port/my.username@somewhere" but got a connection refused, retrying the connection in 11s.
main ↪️ Trying to watch pods on the kubernetes context named "my-ns/some-ocp:port/my.username@somewhere" but got a connection refused, retrying the connection in 9s.
main ↪️ Trying to watch deployments on the kubernetes context named "my-ns/some-ocp:port/my.username@somewhere" but got a connection refused, retrying the connection in 11s.
main ↪️ Trying to watch pods on the kubernetes context named "my-ns/some-ocp:port/my.username@somewhere" but got a connection refused, retrying the connection in 11s.
main ↪️ Trying to watch deployments on the kubernetes context named "my-ns/some-ocp:port/my.username@somewhere" but got a connection refused, retrying the connection in 11s.
main ↪️ Trying to watch pods on the kubernetes context named "my-ns/some-ocp:port/my.username@somewhere" but got a connection refused, retrying the connection in 11s.
main ↪️ Trying to watch deployments on the kubernetes context named "my-ns/some-ocp:port/my.username@somewhere" but got a connection refused, retrying the connection in 11s.

Just to have said this, I don't think the extension should expect the current context being reachable ...

[jeffmaury]

Can you give the extract where the RequestError is happening ?

[jfrantzius]

I can't see it in the logs, will try again

[jfrantzius]

I restarted Podman Desktop, tried again to create the Developer Sandbox Provider, and attached the log (with anonymized non-sense replacements for kube context details)
podman-log.txt

[jeffmaury]

Can't see any error related to Sandbox extension. Does the error happen after you entered the login command or does it happen before ?

[jfrantzius]

afterwards

[jeffmaury]

I managed to reproduce: I just changed the pasted command (changing the port for example) and got a request error so it seems we are trying to connect the cluster.

So maybe it's related to network: are you connect through a proxy ?