juju ssh doesn't work for containers
Bug #1584548 reported by
Menno Finlay-Smits
This bug report is a duplicate of:
Bug #1577638: container addressability Can't juju ssh to lxd-placed container.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
New
|
Undecided
|
Unassigned | ||
Bug Description
You can't ssh to a container using "juju ssh" unless the container has a public IP. To reproduce:
juju bootstrap ...
# add a machine 0 to the model
juju add-machine
# add a LXD container to machine 0
juju add-machine lxd:0
# This hangs because SSH is trying to get to the container's address which is typically not bridged to the outer network.
juju ssh 0/lxd/0
"juju ssh" should proxy through the host machines to get to the container.
Fun things to consider:
- it should work for nested containers
- it should do the right thing when the --proxy option is passed to juju ssh (i.e. tunnel from the controller to the host, and then to the container)
To post a comment you must log in.
