WSA-Community / WSAGAScript

Scripts to install Google Apps into a WSA image. Plus optional root
The Unlicense
3.58k stars 3.53k forks source link

An error occurred when I ran "apply.sh" #91

Open void-cat-0 opened 3 years ago

void-cat-0 commented 3 years ago

It said "find : '/mnt/product/overlay' : no such file or directory"

ArthurWolfhound commented 3 years ago

Check if you don't have any spaces in your path to WSAGAScript. I have the same issue because I placed the folder like that D:\Zulu Storage\WSA\WSAGAScript the space in the "Zulu Storage breaks everything". Try running it from D:\WSA or something like that.

ArthurWolfhound commented 3 years ago

@Dage-Hoo let us know your status, post full error log, or close issue if fixed. Thanks.

irvinekyle commented 2 years ago

I'm having similar issues running apply.sh with a clean directory path.

Logs:

root@DESKTOP-65AIK1G:/mnt/c/WSA/WSAGAScript# sudo ./apply.sh
Modifing build.prop for each image
-> fixing system
-> fixing vendor
-> fixing product
-> fixing system_ext
removing duplicate apps from system
Copying GApps files to system...
Applying root file ownership
Setting directory permissions
Setting file permissions
Applying SELinux security contexts to directories
chcon: failed to get security context of '/mnt/product/app': No data available
chcon: failed to get security context of '/mnt/product/app': No data available
chcon: failed to get security context of '/mnt/product/app': No data available
chcon: failed to get security context of '/mnt/product/app': No data available
chcon: failed to get security context of '/mnt/product/app': No data available
chcon: failed to get security context of '/mnt/product/app': No data available
chcon: failed to get security context of '/mnt/product/etc/permissions': No data available
chcon: failed to get security context of '/mnt/product/priv-app': No data available
chcon: failed to get security context of '/mnt/product/priv-app': No data available
chcon: failed to get security context of '/mnt/product/priv-app': No data available
chcon: failed to get security context of '/mnt/product/priv-app': No data available
chcon: failed to get security context of '/mnt/product/priv-app': No data available
chcon: failed to get security context of '/mnt/product/priv-app': No data available
Applying SELinux security contexts to files
chcon: failed to get security context of '/mnt/product/app/ModuleMetadata/ModuleMetadata.apk': No such file or directory
chcon: failed to get security context of '/mnt/product/app/ModuleMetadata/ModuleMetadata.apk': No such file or directory
chcon: failed to get security context of '/mnt/product/app/ModuleMetadata/ModuleMetadata.apk': No such file or directory
chcon: failed to get security context of '/mnt/product/app/ModuleMetadata/ModuleMetadata.apk': No such file or directory
chcon: failed to get security context of '/mnt/product/app/ModuleMetadata/ModuleMetadata.apk': No such file or directory
chcon: failed to get security context of '/mnt/product/app/ModuleMetadata/ModuleMetadata.apk': No such file or directory
chcon: failed to get security context of '/mnt/product/app/ModuleMetadata/ModuleMetadata.apk': No such file or directory
chcon: failed to get security context of '/mnt/product/app/ModuleMetadata/ModuleMetadata.apk': No such file or directory
chcon: failed to get security context of '/mnt/product/app/ModuleMetadata/ModuleMetadata.apk': No such file or directory
chcon: failed to get security context of '/mnt/product/app/ModuleMetadata/ModuleMetadata.apk': No such file or directory
chcon: failed to get security context of '/mnt/product/app/ModuleMetadata/ModuleMetadata.apk': No such file or directory
chcon: failed to get security context of '/mnt/product/app/ModuleMetadata/ModuleMetadata.apk': No such file or directory
chcon: failed to get security context of '/mnt/product/etc/permissions/privapp-permissions-venezia.xml': No such file or directory
chcon: failed to get security context of '/mnt/product/etc/permissions/privapp-permissions-venezia.xml': No such file or directory
chcon: failed to get security context of '/mnt/product/etc/permissions/privapp-permissions-venezia.xml': No such file or directory
chcon: failed to get security context of '/mnt/product/etc/permissions/privapp-permissions-venezia.xml': No such file or directory
chcon: failed to get security context of '/mnt/product/etc/permissions/privapp-permissions-venezia.xml': No such file or directory
chcon: failed to get security context of '/mnt/product/priv-app/amazon-adm-release/amazon-adm-release.apk': No such file or directory
chcon: failed to get security context of '/mnt/product/priv-app/amazon-adm-release/amazon-adm-release.apk': No such file or directory
chcon: failed to get security context of '/mnt/product/priv-app/amazon-adm-release/amazon-adm-release.apk': No such file or directory
chcon: failed to get security context of '/mnt/product/priv-app/amazon-adm-release/amazon-adm-release.apk': No such file or directory
chcon: failed to get security context of '/mnt/product/priv-app/amazon-adm-release/amazon-adm-release.apk': No such file or directory
chcon: failed to get security context of '/mnt/product/priv-app/amazon-adm-release/amazon-adm-release.apk': No such file or directory
chcon: failed to get security context of '/mnt/product/priv-app/amazon-adm-release/amazon-adm-release.apk': No such file or directory
chcon: failed to get security context of '/mnt/product/priv-app/amazon-adm-release/amazon-adm-release.apk': No such file or directory
Applying SELinux security contexts to props
chcon: failed to get security context of '/mnt/product/etc': No data available
Applying SELinux policy
!! Apply completed !!
root@DESKTOP-65AIK1G:/mnt/c/WSA/WSAGAScript#
NewblyAaron commented 2 years ago

Would also like to confirm this error. Looking at /mnt/product/ there definitely is no overlay directory.

However, /mnt/vendor/ has an overlay directory.

AhanafRASHID commented 1 year ago

Guys, I am totally new in ubuntu so I will not go so far. This SELinux type must be a valid one and available in the policy. To do this , The SELinux must be managed and accessible. I got this form Red Hat Portal