Default /etc/resolv.conf mount incompatible with systemd

[micchickenburger]

Default /etc/resolv.conf mount incompatible with systemd

[micchickenburger]

Related to pull request #50

[yuval-k]

not too familiar with this, how would you check for systemd? do your have a heuristic in mind?

[micchickenburger]

I think it would be fine to just check for the /run/systemd directory. If that directory exists I think it's safe to assume the system uses systemd instead of sysvinit.

[hoshsadiq]

Presuming this isn't just images based on systemd. You could potentially have a base image that already puts the correct file there (e.g. by installing dnsmasq or whatnot). In my opinion that file should either be mounted defensively or the mount should explicitly be enabled through an option rather than by default. Having resolv.conf mounted is a network/host specific use case.

[rgl]

I've tried your workaround with ubuntu 20.04 guest (on a ubuntu 20.04 host with packer-builder-arm-image 0.1.4.5 and packer 1.5.6) and it seems to work, but when I try to execute the shell provisioner with:

"provisioners": [
    {
      "type": "shell",
      "execute_command": "bash {{ .Path }}",
      "script": "provision.sh"
    }
  ]

It errors out with (no mater what I put in execute_command (or even if I remove it), it never executes bash):

==> arm-image: Provisioning with shell script: provision.sh
==> arm-image: chroot: failed to run command ‘/bin/sh’: No such file or directory

Using an "inline": "uname" also fails with the same error.

Do you have any clue of what is going on?

[yuval-k]

closing as fixed by #70