You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched existing issues to check if an issue already exists for my feature request.
Is your feature request related to a problem? Please describe.
Currently Workshop uses proxy devices for containers, and they work nicely. VMs currently require setting nat=true, which in turn requires static IP addresses. Also, VMs don't support proxying unix sockets.
Describe the solution you'd like
We'd like a nat=false implementation of proxy devices, possibly using vsock as a medium.
It should support TCP and UDP connections, but I don't think we have a use case for TCP on one end and UDP on the other.
It should support sending and receiving data over unix sockets (so we can implement SSH agent forwarding), but doesn't need all the bells and whistles that containers have (i.e. no need to work out how to send a live file descriptor over a vsock).
The code should be based on robust implementations of similar features, for example ssh -L and ssh -R, to avoid regressions (e.g. #14972, #15024, #15784) and current bugs on the container side (e.g. #18687).
Describe alternatives you've considered
Every workshop runs an SSH server, so one alternative would be for Workshop to use ssh -L or ssh -R directly. However, Workshop is a short-lived socket-activated daemon, and isn't currently responsible for external processes.
I think LXD is a much better place to put the logic. For example, it can automatically start and stop the proxy processes as instances are started and stopped.
Yes, this has been discussed in the past, and one option would be to bake proxy support into the lxd-agent, which already has an encrypted vsock connection back to the host.
Activity
tomponline commentedon Nov 10, 2026
Yes, this has been discussed in the past, and one option would be to bake proxy support into the lxd-agent, which already has an encrypted vsock connection back to the host.