EMBA docker environment not ready!

[GabrielSchoenweiler]

Hi,
I learned about emba recently and liked the idea. So I decided to give it a quick try.
So I checked out the repo and ran the default installation with sudo ./installer.sh -d.
The installation went fine.

Now, when I try to run emba with my firmware, it keeps on failing with the message "EMBA docker environment not ready!".
I tried the default-scan and default-sbom profiles. Also I tried to only check the dependecies with "-d 1".

I am using kali 6.12.38+kali-amd64 #1 SMP PREEMPT_DYNAMIC Kali 6.12.38-1kali1 (2025-08-12) x86_64 GNU/Linux.
This is, what emba initially outputs:

What am I doing wrong?

[m-1-k-3]

Sorry, but I don't see any error in your screenshot

[GabrielSchoenweiler]

Sorry, I had the error message only in the text.
It is the exact same problem as described by @allopatin.

[GabrielSchoenweiler]

btw., just to have this clear again: I am using kali 6.12.38, which I think is fully supported

[GabrielSchoenweiler]

Thanks for adding and resolving the issue #1773 !
This solved the issue for me.

[m-1-k-3]

perfect. Thank you for the feedback

[allopatin]

running on Ubuntu 25.10

[allopatin]

Yes:

IMAGE                                ID             DISK USAGE   CONTENT SIZE   EXTRA
embeddedanalyzer/emba:1.5.2j         a6a1902d0296       25.6GB         7.44GB    U
embeddedanalyzer/emba:latest         a6a1902d0296       25.6GB         7.44GB    U

[m-1-k-3]

I have seen the same output on an updated kali system. I will adjust it ...

[m-1-k-3]

please test #1775

[allopatin]

It works. But I'd personally suggest this regex instead: embeddedanalyzer/emba([[:space:]]|:latest). This would match your results as well as mine. I think your suggestion from the PR would match the first result in my result which, if multiple image revisions are present, would be the oldest docker image present on the machine which isn't ideal.
Forget this I just realized this is just a general check if an image is present. Doesn't really matter which version.

[m-1-k-3]

yea it is a very generic check. Probably we should adjust it in the future to check the relevant image from the docker-compose file