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
Thanks first of all for this container image, it's a very useful tool for the lazy (me 馃榿), who can't be bothered with setting up QEMU!
I am a relative newbie in the embedded linux space and am trying to leverage this tool to run some automated tests in our ARM based, Raspberry Pi 3 aimed images. We use the Yocto project to create these images which use a different flavor operating system than the one endorsed by the raspberry pi foundation (raspbian), which is why I think I am running into this issue.
As described in the Readme of this repo, I use the following command line to attempt to run a custom Raspberry Pi 3 image:
docker run -it -v /path/to/rpi/image:/sdcard/filesystem.img lukechilds/dockerpi pi3
When running that command I get the following error:
image: /sdcard/filesystem.img
file format: raw
virtual size: 2 GiB (2147483648 bytes)
disk size: 1.12 GiB
Extracting partitions
dd: invalid number '703,3,32'
Extracting boot filesystem
Error: ! Unable to open the input file: /fat.img for reading
Searching for kernel='kernel8.img'
Searching for dtb='bcm2710-rpi-3-b-plus.dtb'
Missing kernel='' or dtb=''
Which makes sense, since when exploring this image via a flashed sd card, I find the following files (apologies for the Windows output format):
I believe the file that should be 'found' here is kernel7.img which is instead of kernel8.img. Seems like this search is somewhat hardcoded, which makes me think that:
Not possible in current release - I am aware that pi2 & pi3 support is experimental,
Somehow configurable at container startup via something like an environment variable.
So, is it 1. or 2.? 馃槄
Also, if someone with Yocto experience on this container reads this, could you either:
Supply a list of changes required to my image to be supported by this container, and/or,
Supply reading material (please not the Mega-Manual! 馃槱) that could help me get to that point?
Used as the custom image file in the docker command to reproduce this issue
Flashed onto an SD card and tested in a physical Raspberry Pi 3 to ensure it works (I tried it) - just sign is as root (no password).
Thanks for reading this if you got this far, please let me know if I have not explained myself enough (I tend to ramble 馃槄) and/or if you have any issue collecting the image file for testing.
Regards
The text was updated successfully, but these errors were encountered:
Hi
Thanks first of all for this container image, it's a very useful tool for the lazy (me 馃榿), who can't be bothered with setting up QEMU!
I am a relative newbie in the embedded linux space and am trying to leverage this tool to run some automated tests in our ARM based, Raspberry Pi 3 aimed images. We use the Yocto project to create these images which use a different flavor operating system than the one endorsed by the raspberry pi foundation (raspbian), which is why I think I am running into this issue.
As described in the Readme of this repo, I use the following command line to attempt to run a custom Raspberry Pi 3 image:
docker run -it -v /path/to/rpi/image:/sdcard/filesystem.img lukechilds/dockerpi pi3
When running that command I get the following error:
Which makes sense, since when exploring this image via a flashed sd card, I find the following files (apologies for the Windows output format):
I believe the file that should be 'found' here is
kernel7.img
which is instead ofkernel8.img
. Seems like this search is somewhat hardcoded, which makes me think that:So, is it 1. or 2.? 馃槄
Also, if someone with Yocto experience on this container reads this, could you either:
Here I provide a minimal working image (~400MB download, be warned!), that runs a bare bones distribution, without our private code. This image file can be:
Thanks for reading this if you got this far, please let me know if I have not explained myself enough (I tend to ramble 馃槄) and/or if you have any issue collecting the image file for testing.
Regards
The text was updated successfully, but these errors were encountered: