We are likely assuming the source image is compliant enough with the LSB[1] which references the Filesystem Hierarchy Standard[2] that specifies a /bin directory which includes the tar command[3]. Any improvement in LSB compliance would be beneficial for the UOS distribution. [1] https://refspecs.linuxfoundation.org/LSB_5.0.0/LSB-Core-generic/LSB-Core-generic/normativerefs.html#STD.FHS [2] https://refspecs.linuxbase.org/fhs [3] https://refspecs.linuxbase.org/FHS_3.0/fhs/ch03s04.html On 23/03/23 21:41, 任亮 wrote: > > I have found the cause of the problem, which is because tar does not > exist in the working directory. > I wonder if there are requirements on the base image when building > from the base image. > > Thank you. > > ------------------------------------------------------------------------ > 发自我的企业微信 > <https://work.weixin.qq.com/wework_admin/user/h5/qqmail_user_card/vc22c69ad124845845?from=myprofile> > > > ----------回复的邮件信息---------- > 任亮<renliang at uniontech.com> 在2023-03-23 周四 15:01写道： > > > Hi > We are using diskimage-builder to make a custom image, There is a > problem in extract_image, The question is chroot: failed to run > command 'bin/tar': No such file or directory, I found the /bin/tar > file in the working directory /tmp/ tmp.00yldwe1xt. But errors are > still being reported. It's not clear if this is a custom image > problem, There are also requirements for custom images. > > ------------------------------------------------------------------------ > 发自我的企业微信 > <https://work.weixin.qq.com/wework_admin/user/h5/qqmail_user_card/vc22c69ad124845845?from=myprofile> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20230324/518eee00/attachment.htm>