Adding systemd-resolved breaks DNS during install with LXC / tteck script about nextcloudpi

[namomitk]

Install was with the Proxmox-Script.

Resolv.conf is changed from being the DNS server set in Proxmox / the LXC to:

nameserver 127.0.0.53
options edns0 trust-ad
search .

[theCalcaholic]

@namomitk I did some more testing and believe that the issue can best be fixed in the install script, not NCP itself (I'll discuss this with ttek in more detail in the downstream issue tomorrow).

For now, you can still install NCP on Proxomox by heading to any storage pool that has CT Templates enabled, go to CT Templates, click "Download from URL" and enter the link to the latest LXC image from the Nextcloudpi releases page.
Then create a container from that template.
I recommend this method anyways, because that way you will get an already tested image instead of running the whole build process which always has a chance to fail.

In my test, I had to set the network device to "static IP" - DHCP didn't seem to work (but I don't think that that's an issue with the container image - I'll need to look into that). But other than that everything worked fine.

[theCalcaholic]

Hm, weird, I had the opposite happening in my LXD build 🤔

Did you install using the official NCP-LXC-Image or via the Proxmox-Script?

[namomitk]

Thanks for looking into it. Always rough building from master. I understand why you couldn’t change the commits. Thanks for the how to.