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
I've already refactored most of that script; would it be a bad idea to add some flag to allow tarball extract failures?
I've also changed the script to allow no metadata archive to be supplied, since an empty one works.
Finally, I see some code for handling uids and gids - but I do not see how it's being used except for one small check. Is this interacting with lxc-create in some way? I also found that lxc-create considers ~/.config/lxc/default.conf, which is confusing because the template script imports the rest. Is there some documentation about what is supposed to handle what in the config parsing process?
The text was updated successfully, but these errors were encountered:
I'm working on rewriting this script:
main...desultory:lxc:main
It fails when importing a gentoo stage3 tarball: https://distfiles.gentoo.org/releases/amd64/autobuilds/20231015T161657Z/stage3-amd64-openrc-20231015T161657Z.tar.xz
I've already refactored most of that script; would it be a bad idea to add some flag to allow tarball extract failures?
I've also changed the script to allow no metadata archive to be supplied, since an empty one works.
Finally, I see some code for handling uids and gids - but I do not see how it's being used except for one small check. Is this interacting with lxc-create in some way? I also found that lxc-create considers ~/.config/lxc/default.conf, which is confusing because the template script imports the rest. Is there some documentation about what is supposed to handle what in the config parsing process?
The text was updated successfully, but these errors were encountered: