lxc: sudo: unable to resolve host
Bug #1328269 reported by
David Britton
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
Unassigned | ||
juju-core |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
this is an annoyance rather than a real error. Still gives an unpolished look.
When you deploy a container (either on the maas provider or the local provider), and login to the container and attempt to use 'sudo', you see:
sudo: unable to resolve host dpb-local-machine-1
Everything works, but with every sudo command you run, you get this. I found a relevant bug which suggests perhaps just a configuration change?
https:/
Work around:
Add the hostname to /etc/hosts
description: | updated |
Changed in juju-core: | |
milestone: | none → next-stable |
importance: | Medium → High |
tags: | added: cts-cloud-review landscape |
tags: | added: cts |
Changed in juju-core: | |
milestone: | 1.21 → 1.22 |
Changed in juju-core: | |
milestone: | 1.22-alpha1 → 1.23 |
Changed in juju-core: | |
milestone: | 1.23 → none |
importance: | High → Medium |
tags: | removed: cts |
tags: | added: canonical-is |
tags: | added: canonical-bootstack |
no longer affects: | juju |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in juju: | |
status: | Triaged → Fix Released |
To post a comment you must log in.
This appears to be fixed in saucy+. Precise may need special attention. From the other bug:
Note that there is an easy workaround by adding the container name to /etc/hosts yourself.