I would expect that since the default behavior for containers is to get a sticky IP from MAAS, that you would be able to connect to any container from the same hosts that can connect to the MAAS nodes.
I wasn't able to recreate the problem locally on either beta6 or tip of master. In both cases, I could juju ssh directly to the container without using --proxy.
However, that was on xenial, and I see you're on trusty, and that may be a key difference. Will try with that tomorrow.
I would expect that since the default behavior for containers is to get a sticky IP from MAAS, that you would be able to connect to any container from the same hosts that can connect to the MAAS nodes.
I wasn't able to recreate the problem locally on either beta6 or tip of master. In both cases, I could juju ssh directly to the container without using --proxy.
However, that was on xenial, and I see you're on trusty, and that may be a key difference. Will try with that tomorrow.