"sudo: unable to resolve host ..." when custom hostname is used.
Bug #1464396 reported by
Simon Eisenmann
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snappy |
Won't Fix
|
Critical
|
Unassigned | ||
Bug Description
When setting a hostname in OEM package.yaml every time sudo is run, it fails to resolve that host name. The host name is not added to /etc/hosts when the snappy image is built.
To reproduce add something like this to your package.yaml
config:
ubuntu-core:
hostname: odroid
Then check /etc/hosts - that hostname needs to be added there, possibly as 127.0.1.1 similar to what the normal Ubuntu is doing.
| Changed in snappy: | |
| status: | New → Triaged |
| importance: | Undecided → Critical |
| summary: |
- "sudo: unable to resolve host ..." + "sudo: unable to resolve host ..." when custom hostname is used. |
Revision history for this message
| Zygmunt Krynicki (zyga) wrote | #1 |
| Changed in snappy: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
I'm marking this bug as won't fix as it was reported in snapd 15.04 era. Please re-open with updated information if the original issue is still a problem for you.