Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rootfs image name #124

Closed
thburghout opened this issue Jan 5, 2024 · 2 comments
Closed

Rootfs image name #124

thburghout opened this issue Jan 5, 2024 · 2 comments

Comments

@thburghout
Copy link

thburghout commented Jan 5, 2024

Hi,

I was updating our layers, and I ran into an issue with an incorrect filename passed to tar.

| NOTE: Unpacking /home/user/Documents/foo/build/tmp-glibc/deploy/images/nedap-foo/foo-base-nedap-foo.tar.bz2 to /home/user/Documents/foo/build/tmp-glibc/work/nedap_foo-oe-linux-gnueabi/foo-image/1.0/root
| tar: /home/user/Documents/foo/build/tmp-glibc/deploy/images/nedap-foo/foo-base-nedap-foo.tar.bz2: Cannot open: No such file or directory
| tar: Error is not recoverable: exiting now

I believe this is due to naming convention change in 4.3 https://docs.yoctoproject.org/singleindex.html#output-file-naming-changes .

The image is now named foo-base-nedap-foo.rootfs.tar.bz2 (recipe foo-base, machine nedap-foo). Note the addition of .rootfs.

I could work around this by setting

GENIMAGE_ROOTFS_IMAGE_FSTYPE = "rootfs.tar.bz2"

in my image recipe. However, I am not sure that this is an appropriate fix.

If there is more information needed, please let me know.

Thanks!

@Bastian-Krause
Copy link
Member

See #123.

@thburghout
Copy link
Author

Apologies, I forgot to take a look at the pull request. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants