Hello, some news about this issue.
Tim pointed me to the docker and the reason why crops container have some
UID:GID manipulation: [see
there](https://github.com/crops/extsdk-container/blob/master/usersetup.py).
I used an ubuntu 20.04 VM to setup a build without docker and I fall into the
exact same problem.
But finally, I found that a workaround by creating and using another working
directory inside my image creation command (though I clearly don't know why
this work and the former way don't, despite it worked with yocto warrior)
Before that, I have a working directory that was created in the bbclass :
```
SQSHDIR = "${S}/sqshimg/${MACHINE}"
do_image_tapos_sqshimg[dirs] += "${SQSHDIR}"
do_image_tapos_sqshimg[cleandirs] += "${SQSHDIR}"
do_image_tapos_sqshimg[recrdeptask] += "do_deploy"
IMAGE_CMD_tapos-sqshimg() {
install -d ${SQSHDIR}
```
I simply replaced the creation command by:
```
IMAGE_CMD_tapos-sqshimg() {
SQSHDIR_WORKDIR=$(mktemp -d)
```
and voilà !
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58810): https://lists.yoctoproject.org/g/yocto/message/58810
Mute This Topic: https://lists.yoctoproject.org/mt/94706311/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
