|
Using Docker containers on Yocto with RISC-V architecture
#meta-virtualization
#yocto
To me, it seems like you need to add some additional kernel configurations for your build, enabling e.g. overlayfs support in your kernel. BR, /Joakim
To me, it seems like you need to add some additional kernel configurations for your build, enabling e.g. overlayfs support in your kernel. BR, /Joakim
|
By
Joakim Roubert
· #7788
·
|
|
Using Docker containers on Yocto with RISC-V architecture
#meta-virtualization
#yocto
Hello Bruce and Jose, Thank you for your valuable input. I needed to update from Honister to Kirkstone. Using Kirkstone, I was to successfully build with meta-virtualization layer and include the CORE
Hello Bruce and Jose, Thank you for your valuable input. I needed to update from Honister to Kirkstone. Using Kirkstone, I was to successfully build with meta-virtualization layer and include the CORE
|
By
jmoreno@...
· #7786
·
|
|
Using Docker containers on Yocto with RISC-V architecture
#meta-virtualization
#yocto
Hello
By
jmoreno@...
· #7785
·
|
|
Using Docker containers on Yocto with RISC-V architecture
#meta-virtualization
#yocto
Hi Jonathan, <jmoreno@...> escreveu no dia quinta, 29/12/2022 à(s) 23:10: This build issue is already fixed on some meta-virtualization git branches. At last master, langdale and
Hi Jonathan, <jmoreno@...> escreveu no dia quinta, 29/12/2022 à(s) 23:10: This build issue is already fixed on some meta-virtualization git branches. At last master, langdale and
|
By
Jose Quaresma
· #7784
·
|
|
Using Docker containers on Yocto with RISC-V architecture
#meta-virtualization
#yocto
riscv isn't an architecture that is built or tested with meta-virt, so while it might be feasible, I don't even know what work would be required to get all the components building for the architecture
riscv isn't an architecture that is built or tested with meta-virt, so while it might be feasible, I don't even know what work would be required to get all the components building for the architecture
|
By
Bruce Ashfield
· #7783
·
|
|
Using Docker containers on Yocto with RISC-V architecture
#meta-virtualization
#yocto
Hello, I am using Yocto on a RISC-V board, Microchip PolarFire Icicle Kit: https://www.microsemi.com/existing-parts/parts/152514 (Board's Yocto directory: https://github.com/polarfire-soc/meta-polarfi
Hello, I am using Yocto on a RISC-V board, Microchip PolarFire Icicle Kit: https://www.microsemi.com/existing-parts/parts/152514 (Board's Yocto directory: https://github.com/polarfire-soc/meta-polarfi
|
By
jmoreno@...
· #7782
·
|
|
Which package provides virt-install CLI tool in Yocto?
#virt-manager
#meta-virtualization
#yocto
#virt-install
#libvirt
Hi, Does anyone know which package provides virt-install CLI tool in Yocto or how to use virt-install tool in yocto environment? I have added below packages in my bb file but I don't see virt-install
Hi, Does anyone know which package provides virt-install CLI tool in Yocto or how to use virt-install tool in yocto environment? I have added below packages in my bb file but I don't see virt-install
|
By
deekshith565@...
· #7210
·
|
|
Where is docker.cfg file in rocko?
#meta-virtualization
#yocto
On Wed, Jan 5, 2022 at 4:46 AM <thitgahamtonghop@...> wrote: > > [Edited Message Follows] > > Hi, > So I am having problem running docker image. When I run command: docker run hello-world, this
On Wed, Jan 5, 2022 at 4:46 AM <thitgahamtonghop@...> wrote: > > [Edited Message Follows] > > Hi, > So I am having problem running docker image. When I run command: docker run hello-world, this
|
By
Bruce Ashfield
· #6994
·
|
|
Where is docker.cfg file in rocko?
#meta-virtualization
#yocto
Hi, So I am having problem running docker image. When I run command: docker run hello-world, this is the output: docker: Error response from daemon: failed to create endpoint elastic_hypatia on networ
Hi, So I am having problem running docker image. When I run command: docker run hello-world, this is the output: docker: Error response from daemon: failed to create endpoint elastic_hypatia on networ
|
By
thitgahamtonghop@...
· #6990
·
Edited
|
|
Building crun does not feth everything in do_fetch
#meta-virtualization
Ah yes, they've committed crimes in autogen.sh, that I hadn't noticed creeping in. I've bumped crun to the latest, and will confirm no network access before pushing. Bruce
Ah yes, they've committed crimes in autogen.sh, that I hadn't noticed creeping in. I've bumped crun to the latest, and will confirm no network access before pushing. Bruce
|
By
Bruce Ashfield
· #6835
·
|
|
Building crun does not feth everything in do_fetch
#meta-virtualization
Bruce, Thank you for the response. I believe I am running into the same issue attempting to build podman with crun as the container runtime. These are the steps I have taken to reproduce the error: -
Bruce, Thank you for the response. I believe I am running into the same issue attempting to build podman with crun as the container runtime. These are the steps I have taken to reproduce the error: -
|
By
...
· #6834
·
|
|
Building crun does not feth everything in do_fetch
#meta-virtualization
All of those dependencies are already specified in the recipe, and in any integration/build testing that I've done, they are all picked up properly. libocispec is directly specified in the SRC_URI and
All of those dependencies are already specified in the recipe, and in any integration/build testing that I've done, they are all picked up properly. libocispec is directly specified in the SRC_URI and
|
By
Bruce Ashfield
· #6823
·
|
|
Building crun does not feth everything in do_fetch
#meta-virtualization
I recently discovered a couple of issues with building crun. The first issue is when using a proxy to download source. crun depends on libocispec which is a git sub-module. The proxy environment varia
I recently discovered a couple of issues with building crun. The first issue is when using a proxy to download source. crun depends on libocispec which is a git sub-module. The proxy environment varia
|
By
Marc Wiz
· #6822
·
|
|
Docker 20.10.3 breaks due to iptables v1.8.7 (legacy) incompatibility
#meta-virtualization
Adding kernel-modules did the trick, the docker daemon issued iptables command now works and supports --to-destination for dnat. Thank-you Bruce for taking the time to explain, I've learned a ton in t
Adding kernel-modules did the trick, the docker daemon issued iptables command now works and supports --to-destination for dnat. Thank-you Bruce for taking the time to explain, I've learned a ton in t
|
By
Stephen
· #6812
·
|
|
Docker 20.10.3 breaks due to iptables v1.8.7 (legacy) incompatibility
#meta-virtualization
In the K3S recipe, we actually have finer grained RRECOMMENDS than the docker recipes (due to the way k3s was developed and integrated). In K3S, I'm currently tracking: RRECOMMENDS:${PN} = "\ kernel-m
In the K3S recipe, we actually have finer grained RRECOMMENDS than the docker recipes (due to the way k3s was developed and integrated). In K3S, I'm currently tracking: RRECOMMENDS:${PN} = "\ kernel-m
|
By
Bruce Ashfield
· #6811
·
|
|
Docker 20.10.3 breaks due to iptables v1.8.7 (legacy) incompatibility
#meta-virtualization
Yes, you're spot on! Running the script reviled the following. The issue I'm having now is finding the correct way of including the configs, I tried setting them in my myKernelConfigs.cfg and IMAGE_IN
Yes, you're spot on! Running the script reviled the following. The issue I'm having now is finding the correct way of including the configs, I tried setting them in my myKernelConfigs.cfg and IMAGE_IN
|
By
Stephen
· #6809
·
|
|
Docker 20.10.3 breaks due to iptables v1.8.7 (legacy) incompatibility
#meta-virtualization
It'll be the iptables and cgroups options that are causing issues. The standard layers and kernel are extensively tested with meta-virt, so there really shouldn't be something missing. You can also in
It'll be the iptables and cgroups options that are causing issues. The standard layers and kernel are extensively tested with meta-virt, so there really shouldn't be something missing. You can also in
|
By
Bruce Ashfield
· #6805
·
|
|
Docker 20.10.3 breaks due to iptables v1.8.7 (legacy) incompatibility
#meta-virtualization
Thanks for the reply Bruce __ Let me know if these details help? root@generic-arm64:~# uname -r 5.10.46-yocto-standard Only setting these two kernel configs at the moment: CONFIG_ENA_ETHERNET=y CONFIG
Thanks for the reply Bruce __ Let me know if these details help? root@generic-arm64:~# uname -r 5.10.46-yocto-standard Only setting these two kernel configs at the moment: CONFIG_ENA_ETHERNET=y CONFIG
|
By
Stephen
· #6804
·
|
|
Docker 20.10.3 breaks due to iptables v1.8.7 (legacy) incompatibility
#meta-virtualization
<stephibb=amazon.co.uk@...> wrote: It's your kernel configuration, coupled with the iptables modules available .. but most often, it is a missing kernel module. So without knowing e
<stephibb=amazon.co.uk@...> wrote: It's your kernel configuration, coupled with the iptables modules available .. but most often, it is a missing kernel module. So without knowing e
|
By
Bruce Ashfield
· #6803
·
|
|
Docker 20.10.3 breaks due to iptables v1.8.7 (legacy) incompatibility
#meta-virtualization
Hello all! The current meta-virtualisation docker is incompatible with the legacy v1.8.7 iptables. Docker version 20.10.3, build 41b3ea7e47 http://layers.openembedded.org/layerindex/recipe/176817/ ipt
Hello all! The current meta-virtualisation docker is incompatible with the legacy v1.8.7 iptables. Docker version 20.10.3, build 41b3ea7e47 http://layers.openembedded.org/layerindex/recipe/176817/ ipt
|
By
Stephen
· #6796
·
|