This is because you’re still pointing the installation image to the official samba one!
Changing this line with your image should make everything work fine.
1 Like
yes much more success now 
Samba count provider seems to be running!
Still quite some errors in the logs, (see end of gist) as said was able to add an user.
The initial installation of the node pulls in two images from ghcr.io/nethserver/ (loki and ldapproxy),
$ podman image list --all
REPOSITORY TAG IMAGE ID CREATED SIZE
ghcr.io/nethserver/traefik 2.1.0 39961d94bd8d 9 days ago 132 kB
ghcr.io/tbaile/core main a68ba2b77818 10 days ago 139 MB
ghcr.io/tbaile/redis main 6df53c5d2d03 10 days ago 42.8 MB
ghcr.io/tbaile/rsync main 2b3a46ae2be6 10 days ago 9.48 MB
ghcr.io/tbaile/restic main f287a15011df 10 days ago 86.1 MB
ghcr.io/nethserver/ldapproxy 1.0.0 22e5405803da 2 months ago 26.8 kB
docker.io/grafana/promtail 2.9.2 c04c05a00c6c 2 months ago 193 MB
ghcr.io/nethserver/loki 1.0.0 9ccb9414fb0a 6 months ago 22.2 kB
that can no be right … or is it?
Modules are actually separated this way:
There’s the MODULE IMAGE, which contains the following files:
- the imageroot of the image (systemd services, cluster hooks for actions, configuration…)
- module own UI, the same UI that helps you configure the module
- additional can be found here
This images should be “arch-less” (unless, like the core, has binaries), and can be downloaded by every client despite the architecture.
This is not the case for the images that are used to run the actual software, usually specified in the images label of the image.
The “running” images, often come directly from the companies, and they most likely already have a ARM version built, which podman automatically pulls and runs. This is true for the traefik instance that you’re using to serve the main UI.
that can no be right … or is it?
This comes by a per-module basis, if a module just uses the base image from official sources then yes, the module is installed correctly and the arm version of the container is happily running in the background.
If for necessities the container needs to be customized heavily (I.E. installing additional software) then you need to build the container for all the architectures that you want it available for. (this second case is exactly why building samba provides two containers, the module container and the runtime container)
Additional info will be probably available during Fosdem 
3 Likes
NDA sighted…
2 Likes
Thanks for the extensive explanation!
And I will be patient now 
2 Likes
Let’s give this a little kick…. Just curious what the current situation is. Pi 5 is out and other more powerfull/capable ARM hardware.