Containers with host networking cannot resolve their hostname #994
Labels
low-hanging fruit
Easy to fix issue
Needs discussion
The fix for this needs to be discussed.
Needs more investigation
More investigation is needed to find the cause or fix
This seems to come from
/etc/hosts
not being populated with the devices' hostname, but this happens on normal docker. It's not clear if this is a bug in the supervisor or balenaEngine (or even the OS itself).Either way, this can be solved on the supervisor side by adding
<hostname>:127.0.0.1
to theextraHosts
array on a container with host networking.The text was updated successfully, but these errors were encountered: