It’s predictable based upon the “slot” the network card is in. Previously, it was non-determinate whether or not you’d get eth1, eth2, eth3, etc depending on which stage the card which picked up by the OS. Now a given network card will always get the same name. Of course, this mostly just seems to be a change for changes’ sake from the perspective of a virtualised environment!
Re netplan apply: Does the OS do this on reboot? It should read the config in then. On Monday, 15 June 2020 21:20:29 UTC+1, Elhanan Maayan wrote: > > i figured out what was wrong, it's the ens33, that had it , it was mean to > be ens160 (i have no idea what this "predictable naming" scheme means > > now my problem is how to have packer do " netplan apply" after i sed the > netplan renderer in the late command from networkd to NetworkManager > > On Mon, Jun 15, 2020 at 6:59 PM Elhanan Maayan <[email protected] > <javascript:>> wrote: > >> thanks, that Alt+F2 really helped, in getting into linux ,didn't help so >> much in to see why it's hanging >> [image: image.png] >> >> i'm seriously considering to switch to centos, it also depends if i can >> find maven plugin that doesn't centos to create a package >> >> with all the changes canonical is making (switching to netplan, using >> cloud-init) pissing of users, breakign backward compatiblity and so on.. >> >> (but then i would dependent on that plug-in) >> >> >> On Mon, Jun 15, 2020 at 5:16 PM Nick Charlton <[email protected] >> <javascript:>> wrote: >> >>> The installer failing, or hanging was a consistent problem I was facing >>> too. If you pull up a tty, you can access the install log (you'll likely >>> need to make your build not headless to be able to do this if you haven't >>> already), from the bottom of the post: >>> >>> To solve issues along the way, I: >>> >>> * Used Alt + F2 to get a working console when the installer failed or >>> got stuck, >>> * Read the output of /var/log/installer/subiquity-debug.log to get the >>> network configuration correct, >>> * …and /var/log/syslog to debug the YAML parsing issues around the >>> late-commands. >>> >>> >>> In general, I've found the new installer works okay, just the failure >>> cases are very confusing to dig your way out of. >>> >>> Re: networking: Yeah, Packer 1.6 will fix that networking problem. I >>> have a bunch of places to go and change this and until then the workaround >>> is fine. >>> >>> I'd be interested in hearing what, if any, other issues you had with >>> that example repo though. >>> >>> - N >>> >>> On Monday, 15 June 2020 14:19:06 UTC+1, Elhanan Maayan wrote: >>>> >>>> hi, i've seen several versions of this boot commands, yours was one of >>>> the ones that didn't work , but that did work >>>> was this, (with that autoinstall before the ---) otherwise i would just >>>> get the regular boot >>>> >>>> >>>> "<esc><wait><esc><wait><f6><wait><esc><wait>", >>>> "<bs><bs><bs><bs><bs>", >>>> "autoinstall ds=nocloud-net;s=http://{{ .HTTPIP }}:{{ .HTTPPort }}/ ", >>>> "--- <enter>" >>>> >>>> >>>> >>>> yes there is a legacy iso, but it's considered discontinued >>>> /unsupported >>>> >>>> i do have other issues, each time i specify packages: and other >>>> packages i want to import , the installer hangs or crashes , and i can't >>>> the crash output >>>> i also want it to start with NetworkManager in netplan and i think it >>>> also crashes when i try that. >>>> >>>> additionaly i think packer 1.6.0 solved the problem with ssh and ip >>>> https://github.com/hashicorp/packer/issues/8528 >>>> >>>> >>>> >>>> >>>> On Monday, June 15, 2020 at 1:31:52 PM UTC+3, Nick Charlton wrote: >>>>> >>>>> The new installer needs a new boot command and preseed approach >>>>> entirely. These should help you out: >>>>> >>>>> https://github.com/nickcharlton/packer-ubuntu-2004 >>>>> >>>>> https://nickcharlton.net/posts/automating-ubuntu-2004-installs-with-packer.html >>>>> >>>>> Back when I published these, I did try it out with VirtualBox and it >>>>> worked (I happen to have a preference for VMWare but it's not important >>>>> to >>>>> this). >>>>> >>>>> I _think_ there's an ISO that Ubuntu host that continues to have the >>>>> old installer (which I think bento might have gone with?), but it'd be >>>>> more >>>>> future proof to embrace the new installer. >>>>> >>>>> Let me know if you have any questions! >>>>> >>>>> - Nick >>>>> >>>>> On Saturday, 13 June 2020 19:29:32 UTC+1, Benjamin Lu wrote: >>>>>> >>>>>> Sorry, yeah well it seems like it only has the live dvd which doesn't >>>>>> have. the actual without the live one. I'm sure it'll come out when >>>>>> 20.04.1 >>>>>> comes out. my best guess. >>>>>> >>>>>> http://cdimage.ubuntu.com/ubuntu/releases/20.04/release/ubuntu-20.04-live-server-arm64.iso >>>>>> >>>>>> On Saturday, June 13, 2020 at 11:22:53 AM UTC-7, Benjamin Lu wrote: >>>>>>> >>>>>>> Opps. sorry. >>>>>>> >>>>>>> On Sat, Jun 13, 2020 at 10:41 AM Elhanan Maayan <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> this is for ubuntu 12 >>>>>>>> >>>>>>>> On Fri, Jun 12, 2020 at 7:45 PM Benjamin Lu <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> I might be wrong,, but do u have this settings >>>>>>>>> >>>>>>>>> "checksum_type": "sha256", >>>>>>>>> "checksum_url": " >>>>>>>>> http://cdimage.ubuntu.com/ubuntu/releases/12.04/release/SHA256SUMS >>>>>>>>> ", >>>>>>>>> "image_url": " >>>>>>>>> http://cdimage.ubuntu.com/ubuntu/releases/12.04/release/ubuntu-12.04.5-dvd-amd64.iso >>>>>>>>> " >>>>>>>>> >>>>>>>>> >>>>>>>>> On Friday, June 12, 2020 at 3:23:49 AM UTC-7, Elhanan Maayan wrote: >>>>>>>>>> >>>>>>>>>> ubuntu 20 decided to ditch the D-I installer, and go with >>>>>>>>>> subiquity something that some folks think unstable, >>>>>>>>>> >>>>>>>>>> there's only one example of how to do (for vmware), and when i >>>>>>>>>> tried it , it didn't work (i was stuck in language selection) >>>>>>>>>> >>>>>>>>>> i know they still provide a distor with legacy d-i, but they say >>>>>>>>>> it's not supported. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> https://discourse.ubuntu.com/t/server-installer-plans-for-20-04-lts/13631/58 >>>>>>>>>> >>>>>>>>> -- >>>>>>>>> This mailing list is governed under the HashiCorp Community >>>>>>>>> Guidelines - https://www.hashicorp.com/community-guidelines.html. >>>>>>>>> Behavior in violation of those guidelines may result in your removal >>>>>>>>> from >>>>>>>>> this mailing list. >>>>>>>>> >>>>>>>>> GitHub Issues: https://github.com/hashicorp/packer/issues >>>>>>>>> IRC: #packer-tool on Freenode >>>>>>>>> --- >>>>>>>>> You received this message because you are subscribed to a topic in >>>>>>>>> the Google Groups "Packer" group. >>>>>>>>> To unsubscribe from this topic, visit >>>>>>>>> https://groups.google.com/d/topic/packer-tool/SByQFIdRmaY/unsubscribe >>>>>>>>> . >>>>>>>>> To unsubscribe from this group and all its topics, send an email >>>>>>>>> to [email protected]. >>>>>>>>> To view this discussion on the web visit >>>>>>>>> https://groups.google.com/d/msgid/packer-tool/b99eabc5-6adf-438e-8fb2-fa9550148d17o%40googlegroups.com >>>>>>>>> >>>>>>>>> <https://groups.google.com/d/msgid/packer-tool/b99eabc5-6adf-438e-8fb2-fa9550148d17o%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>>> . >>>>>>>>> >>>>>>>> -- >>>>>>>> This mailing list is governed under the HashiCorp Community >>>>>>>> Guidelines - https://www.hashicorp.com/community-guidelines.html. >>>>>>>> Behavior in violation of those guidelines may result in your removal >>>>>>>> from >>>>>>>> this mailing list. >>>>>>>> >>>>>>>> GitHub Issues: https://github.com/hashicorp/packer/issues >>>>>>>> IRC: #packer-tool on Freenode >>>>>>>> --- >>>>>>>> You received this message because you are subscribed to the Google >>>>>>>> Groups "Packer" group. >>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>> send an email to [email protected]. >>>>>>>> To view this discussion on the web visit >>>>>>>> https://groups.google.com/d/msgid/packer-tool/CAETAEKJNxmqefpxy34O-AyTD9bY_2WT9QXJbZPFaWywbC7H2ZA%40mail.gmail.com >>>>>>>> >>>>>>>> <https://groups.google.com/d/msgid/packer-tool/CAETAEKJNxmqefpxy34O-AyTD9bY_2WT9QXJbZPFaWywbC7H2ZA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>>>>> . >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Benjamin Lu >>>>>>> WordPress Theme & Plugin Developer >>>>>>> WordPress Theme Review Team >>>>>>> Website: Portfolio <https://benjlu.com> >>>>>>> Website: Blog <https://benlu.blog> >>>>>>> WordPress: Profile <https://profiles.wordpress.org/benlumia007> >>>>>>> >>>>>> -- >>> This mailing list is governed under the HashiCorp Community Guidelines - >>> https://www.hashicorp.com/community-guidelines.html. Behavior in >>> violation of those guidelines may result in your removal from this mailing >>> list. >>> >>> GitHub Issues: https://github.com/hashicorp/packer/issues >>> IRC: #packer-tool on Freenode >>> --- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "Packer" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/packer-tool/SByQFIdRmaY/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected] <javascript:>. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/packer-tool/6980d3cf-6de1-44d4-92f1-44f2e23e05fao%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/packer-tool/6980d3cf-6de1-44d4-92f1-44f2e23e05fao%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/hashicorp/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/04f14f22-c459-4e2a-b8e9-9ed8dc2bec31o%40googlegroups.com.
