EVerest / everest-demo

EVerest demo: Dockerized demo with software in the loop simulation
Apache License 2.0
11 stars 13 forks source link

Add dockerfile to create a docker container that builds yocto images #33

Open jhoshiko opened 3 months ago

jhoshiko commented 3 months ago

Added a dockerfile for building a docker container that can build yocto images. Included yocto release files that are unzipped when building the docker container.

@couryrr-afs @drmrd This PR has a simple dockerfile that is automated to build the yocto core-image-minimal target. You can edit this file to add steps for custom layers and change the target to another.

From running the oe-init-build-env script:

You can now run 'bitbake <target>

Common targets are:
    core-image-minimal
    core-image-full-cmdline
    core-image-sato
    core-image-weston
    meta-toolchain
    meta-ide-support

I built the dockerfile following the steps found here, which I would recommend referring to when you edit the dockerfile.

shankari commented 3 months ago

@jhoshiko can you fix the issues/best practices reported by the static code analysis?

drmrd commented 3 months ago

Thanks for this, @jhoshiko! I will give it a try on my system as I'm experimenting with building Yocto-based distros.

Out of curiosity. Is there a reason you built an image manually rather than using the CROPS image that is recommended in recent editions of the Yocto Project Quick Build?

drmrd commented 3 months ago

Ah I just realized that the reasons can be gleaned from discussions on the private issue tracker for our project. It would be great to have those findings summarized and captured in a README.md in the same directory as the Dockerfile.

jhoshiko commented 3 months ago

can you fix the issues/best practices reported by the static code analysis?

@shankari updated!

shankari commented 3 months ago

@jhoshiko can you confirm that you have built the yocto image after these changes, and that it works?

jhoshiko commented 3 months ago

@shankari The image is building for me, but similar to when we were building them before, I run out of memory and it crashes before it can complete. I'll need someone with a beefy workstation who can test this to completion.