Repository navigation
iii worker add attempts to pull local Docker image from registry
#1728
Answered by
anthonyiscoding
Jun 1, 2026
Replies: 2 comments 2 replies
|
hey @GovIndLok Thanks for detailed issue and sharing screenshot. You're correct to point this issue, I have assigned dedicated engineer. Expect fix soon. |
0 replies
|
hey @GovIndLok, At the moment, iii does not support the Docker daemon. However, we do have full support for OCI images, so you can use a local registry. Here’s a quick setup you can follow: We will keep this issue open for now. If more users need Docker daemon support, we can prioritize adding it in the future. |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment

@GovIndLok
What happened in your screenshot is that iii worker checked our registry for a worker with the name caller-worker and didn't find one. iii worker is primarily a way to download worker images from various remote repositories or local folders and run them in a microvm.
Local docker images can be run and tested like any other docker image: