Indeed it does! I just ran a complete test with this on the server: socat TCP-LISTEN:8443,fork UNIX-CLIENT:/var/lib/lxd/unix.socket &
and this on the client: socat UNIX-LISTEN:/var/lib/lxd/unix.socket,unlink-early,mode=666,fork TCP:10.43.42.59:8443 & After two or three runs lxd locks up and needs to be restarted, but that happens with the "real" port and locally too, so that's a separate issue (bug 1531768). So I think this is working. Should we close this bug (which so far was really a support request, thanks!), or keep it open for making this easier/more obvious in lxd? Like an "lxc config set core.remote unsafe" option? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1538174 Title: ways to speed up overhead of "lxc exec" on remote containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1538174/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
