path: root/doc/forum/__34__predictable__34___network_interface_names.mdwn
diff options
authordavid2018-10-14 12:50:31 +0000
committeradmin2018-10-14 12:50:31 +0000
commit7dbd17bc4b020e0a22c5dee0dc38b5681470bb0c (patch)
tree9cf0ae4a656c63b3786cadd88a2cb34b8879811f /doc/forum/__34__predictable__34___network_interface_names.mdwn
parent14e57776922fdb0fcfc689160b7b5f7fce3ce056 (diff)
Diffstat (limited to 'doc/forum/__34__predictable__34___network_interface_names.mdwn')
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/forum/__34__predictable__34___network_interface_names.mdwn b/doc/forum/__34__predictable__34___network_interface_names.mdwn
new file mode 100644
index 00000000..88b4b414
--- /dev/null
+++ b/doc/forum/__34__predictable__34___network_interface_names.mdwn
@@ -0,0 +1,3 @@
+When using propellor to install/create VM images, one naturally wants to set some kind of sane network configuration. Unfortunately the name of the network interface in the guest (or newly installed system) varies according to the hardware setup. As a concrete example, in a newly created stretch amd64 image it is ens0, while in a stretch s390x image it is enc0. I guess the Debian installer must have some way of figuring this out and creating a sane /etc/network/interfaces. Is this something that Property.DiskImage can help with, or do I need to carry per-VM configuration information? I don't mind so much the extra config info, but it's a bit annoying that I need to boot the vm to see what the network device is called.
+I guess the Luddite solution is to turn off interface renaming via boot options; I'm not sure that option will always be available to me, e.g. when deploying images on someone else's host.