#36 have a look here ;)

@Siddius Great news, I will try it.

UPDATE:
@Siddius I am getting an error when using your branch:

| '+v8' is not a recognized feature for this target (ignoring feature)
| error: build failed
| WARNING: exit code 101 from a shell command.
| 
ERROR: Task (/home/vjdaemp/Jetson/Build/jetson-nano-dev-kit/meta-iotedge/recipes-core/iotedge-cli/iotedge-cli_1.0.9.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 5286 tasks of which 5275 didn't need to be rerun and 1 failed.
|
Summary: 1 task failed:
  /home/vjdaemp/Jetson/Build/jetson-nano-dev-kit/meta-iotedge/recipes-core/iotedge-cli/iotedge-cli_1.0.9.bb:do_compile
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Any ideas?

Update: The +v8 related error was coming from meta-rust (master). I reverted to an older version of meta-rust and am now receiving a different issue related to meta-iotedge:

ERROR: Nothing PROVIDES 'docker' (but /home/vjdaemp/Jetson/Build/jetson-nano-devkit/meta-iotedge/recipes-core/iotedge-daemon/iotedge-daemon_1.0.9.bb DEPENDS on or otherwise requires it). Close matches: docker-ce runc-docker docker-moby docker-ce RPROVIDES docker NOTE: Runtime target 'iotedge-daemon' is unbuildable, removing... Missing or unbuildable dependency chain was: ['iotedge-daemon', 'docker'] ERROR: Required build target 'core-image-base' has no buildable providers. Missing or unbuildable dependency chain was: ['core-image-base', 'iotedge-daemon', 'docker']

I tried removing docker from DEPENDS in iotedge-daemon.inc and then encountered a different error:

Running groupadd commands...
Running useradd commands...
useradd: group 'docker' does not exist
WARNING: exit code 1 from a shell command.

ERROR: Logfile of failure stored in: /home/vjdaemp/Jetson/Build/jetson-nano-devkit/poky/build/tmp/work/aarch64-poky-linux/iotedge-daemon/1.0.9-r0/temp/log.do_prepare_recipe_sysroot.2724
ERROR: Task (/home/vjdaemp/Jetson/Build/jetson-nano-devkit/meta-iotedge/recipes-core/iotedge-daemon/iotedge-daemon_1.0.9.bb:do_prepare_recipe_sysroot) failed with exit code '1'

@Siddius Do you know how to resolve these errors, or can you recommend which version of meta-rust you used to build successfully? I am trying to build meta-iotedge for zeus.

By the way, I am new to yocto so I may be missing something.

Thanks!
Vincent

@vjdaemp yeah this error with docker you get because iotegde relies on docker. Add docker-ce to your installed packages. in local.conf for example:
IMAGE_INSTALL_append = " docker-ce"

and DISTRO_FEATURES_append = " virtualization" like discribed in example conf here:

I was using master or rust-meta commit a012a1027defe28495f06ed522a7a82bdd59a610

@Siddius Thanks for your work so far! I encounter the following Errors:

No recipes available for:
  /sources/meta-iotedge/recipes-devtools/cargo/cargo_1.41.0.bbappend

and

ERROR: Nothing PROVIDES 'docker' (but sources/meta-iotedge/recipes-core/iotedge-daemon/iotedge-daemon_1.0.9.bb DEPENDS on or otherwise requires it). Close matches:
  docker-ce
  runc-docker
  docker-moby
  docker-ce RPROVIDES docker

ERROR: Nothing RPROVIDES 'iotedge-daemon-dev' (but /sources/meta-iotedge/recipes-core/iotedge-daemon/iotedge-daemon_1.0.9.bb RDEPENDS on or otherwise requires it)
No eligible RPROVIDERs exist for 'iotedge-daemon-dev'

I added IMAGE_INSTALL_append = " docker-ce" to my local.conf and edited the first line of iotedge-daemon.inc
from
DEPENDS += "openssl docker virtual/libiothsm"
to
DEPENDS += "openssl docker-ce virtual/libiothsm"
which seemes to fix it?

Can you help me out here?

@mirzabrc i am sorry you are totally right, changed to virtual/docker Siddius@b9a368f

have you checked out https://github.com/meta-rust/meta-rust ?
also added fix for 1.43 in Siddius@39a4bcd

@Siddius thanks for your fast reply! I have checked out meta-rust and added it as a layer in bblayers.conf. *
The error remains the same:

ERROR: No recipes available for:
  (...)/sources/meta-iotedge/recipes-devtools/cargo/cargo_1.43.0.bbappend

Any idea what's missing?

@mirzabrc layers.conf ? layers are configured in bblayers.conf right ?

@mirzabrc it should be fine if you work with the master branch of meta-rust.
If you use the commit hash i mentioned earlier, cargo_1.43.0.bb is not present. so you can just delete cargo_1.43.0.bbappend

@Siddius When using meta-rust master I get the same +v8 related error as @vjdaemp
I will revert to meta-rust commit a012a1027defe28495f06ed522a7a82bdd59a610 and give an update later. I removed cargo_1.43.0.bbappend.
Update: The error still remains.
`

| '+v8' is not a recognized feature for this target (ignoring feature)

ERROR: Task (/sources/meta-iotedge/recipes-core/iotedge-cli/iotedge-cli_1.0.9.bb:do_compile) failed with exit code '1'`

Any idea what might cause this?

Also virtual/docker does not work for me, I had to change it to docker-ce.
local.conf:
IMAGE_INSTALL_append = " docker-ce iotedge-cli iotedge-daemon libiothsm-std"
iotedge-daemon.inc:

DEPENDS += "openssl docker-ce virtual/libiothsm"
RDEPENDS_${PN} += "virtual/libiothsm docker-ce"

The "'+v8' is not a recognized feature for this target (ignoring feature)" message is just an warning, not the actual error, see:
meta-rust/meta-rust#293
which fixes this warning and
#58
which fixes compatibility with newer rust.

@shr-project @Siddius I am building Yocto image for jetson tx2 and got stuck with this error.
TE: Runtime target 'iotedge-daemon' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['iotedge-daemon']
ERROR: Required build target 'core-image-minimal' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-minimal', 'iotedge-daemon']

The commit id of the repositories are
Submodule path 'repos/meta-mender': checked out 'e47297c6aee747c331663d8acb933e85d3d55812'
Submodule path 'repos/meta-mender-community': checked out '2f52cf4948bc964f1e5f3f4193b7cf33c1b13037'
Submodule path 'repos/meta-openembedded': checked out '814eec96c2a29172da57a425a3609f8b6fcc6afe'
Submodule path 'repos/meta-tegra': checked out '227c8ba5bd69a62ce86420b7833befcbb57bc33f'
Submodule path 'repos/meta-tegra-community': checked out '4539e0ae1f8145d8c01c190bad650d5adce0c620'
Submodule path 'repos/meta-virtualization': checked out 'f0d8a55c220fdec46927c106568657b725e17126'
Submodule path 'repos/poky': checked out '0810ac6b926cd901f0619e95f367efc79d4c3159'

meta-iotedge : '6840cf2afb51b4f2c535a05d5635736652f664f7'.
meta- rust : 3b783652cc9e0e0ff95fdf151eab3e178b5f1667

please help me to fix this bug

@vaishnavils97 I'm not interested in this layer anymore and removed it from all our builds, see #38 and the pending PRs, I recommend to stop using it as well.

@shr-project , so should I have to switch to some other branch instead of dunfell. Can you please suggest a solution?

any update on this issue ?

Closing. The latest 1.4 recipes are in the Dunfell branch. We're not planning to port them to older branches, but are open to reviewing a pull request.