You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today I used this script to add a package and an autoinstall config to the installer. During the installation I noticed that the name resolution was not working and looking into /etc showed me an incorrectly static resolv.conf and a resolv.conf.tmp symlink.
I looked into the source code and tracked it down to the setup_rootfs() function. This function calls the context method add_sys_mounts() which adds a _pre_repack callback, to restore the original resolv.conf. After this setup_rootfs() addes a _pre_repack callback too, which creates the custom squashfs. Since pre_repack hooks are later called in reverse by the repack() method, the custom squashfs is build before the original resolv.conf is restored.
For myself I fixed it by adding the pre_repack hook from setup_rootfs to the front of the list. I don't know if there are any side effects doing it this way if a more complicated action.yaml is used, because mine is very simple:
Adding it to the start of the whole list brought some other problems with it, so I added the _pre_repack hook from setup_rootfs before the one from add_sys_mounts. These are my two patches to archive this:
Today I used this script to add a package and an autoinstall config to the installer. During the installation I noticed that the name resolution was not working and looking into
/etc
showed me an incorrectly staticresolv.conf
and aresolv.conf.tmp
symlink.I looked into the source code and tracked it down to the
setup_rootfs()
function. This function calls the context methodadd_sys_mounts()
which adds a_pre_repack
callback, to restore the originalresolv.conf
. After thissetup_rootfs()
addes a_pre_repack
callback too, which creates the custom squashfs. Since pre_repack hooks are later called in reverse by therepack()
method, the custom squashfs is build before the originalresolv.conf
is restored.For myself I fixed it by adding the pre_repack hook from
setup_rootfs
to the front of the list. I don't know if there are any side effects doing it this way if a more complicated action.yaml is used, because mine is very simple:The text was updated successfully, but these errors were encountered: