# Docker builder obsolete

**URL:** <https://www.wago.community/t/docker-builder-obsolete/2603>\
**Category:** Hardware and Linux\
**Tags:** docker\
**Created:** [February 27, 2026, 3:42pm UTC](https://www.wago.community/t/docker-builder-obsolete/2603 "2026-02-27T15:42:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Louis](https://avatars.discourse-cdn.com/v4/letter/l/ecb155/32.png) [@Louis](https://www.wago.community/u/Louis)\
**Post date:** [February 27, 2026, 3:42pm UTC](https://www.wago.community/t/docker-builder-obsolete/2603/1 "2026-02-27T15:42:51Z")

</div>

Hello everyone,

Actually, I would like to report a bug regarding the latest firmware for the CC100:

CC100\_V040809\_30

I am currently trying to build a Docker container on the controller. It works fine on my PC, but when I attempt the same via SSH on the controller, I receive the following error message:

 ![image](https://us1.discourse-cdn.com/flex016/uploads/wago/original/2X/d/d227ef0671b1cdaa592d88499b997b442dc7065c.png)

If this is indeed the case, I would expect that the firmware includes buildx by default.

It would be great if I could build the containers directly on the controller. This would save the hassle of transferring pre-built Docker images and specifying specific paths for execution. Is there any way for a user to install buildx on the CC100?

Thank you in advance!

Louis

---

<div class="post-metadata">

**Author:** ![quenorha](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/quenorha/32/429_2.png) [@quenorha](https://www.wago.community/u/quenorha)\
**Post date:** [March 2, 2026, 7:09am UTC](https://www.wago.community/t/docker-builder-obsolete/2603/2 "2026-03-02T07:09:42Z")

</div>

The docker build is possible on the target itself.  
The error is related to the argument --progress.  
Try without this parameter, it should work.

---

<div class="post-metadata">

**Author:** ![WagoDamRud](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/wagodamrud/32/258_2.png) [@WagoDamRud](https://www.wago.community/u/WagoDamRud)\
**Post date:** [March 2, 2026, 11:06pm UTC](https://www.wago.community/t/docker-builder-obsolete/2603/3 "2026-03-02T23:06:10Z")

</div>

btw, I prefer to run Portainer on my computer and Portainer Agent on CC100 (or other device) so this way other devices are environments available from my computer. You can build images based on pasted Dockerfile, \*.tar with Dockerfile inside or even github repository (you can add key to your private repository!).

 ![image](https://us1.discourse-cdn.com/flex016/uploads/wago/original/2X/7/726b5bf6bcda52cc75666126017fcb6f6b70ef91.png)

---

<div class="post-metadata">

**Author:** ![quenorha](https://sea2.discourse-cdn.com/flex016/user_avatar/www.wago.community/quenorha/32/429_2.png) [@quenorha](https://www.wago.community/u/quenorha)\
**Post date:** [March 3, 2026, 7:06am UTC](https://www.wago.community/t/docker-builder-obsolete/2603/4 "2026-03-03T07:06:09Z")

</div>

I’ve recently found Dockhand, which is quiet similar to Portainer.  
Less features but maybe easier to use.

> **[Dockhand - Modern Docker Management](https://dockhand.pro/)**
>
> A powerful, intuitive Docker platform for everyone. Real-time container management, Compose stacks, Git deployments, and SSO - all free.

---

<div class="post-metadata">

**Author:** ![Louis](https://avatars.discourse-cdn.com/v4/letter/l/ecb155/32.png) [@Louis](https://www.wago.community/u/Louis)\
**Post date:** [March 5, 2026, 12:55pm UTC](https://www.wago.community/t/docker-builder-obsolete/2603/5 "2026-03-05T12:55:50Z")

</div>

I have found that exporting tar files locally and importing them into the Docker repository on the controller is not as tedious as expected.

Nevertheless, thank you very much, everyone, for the advice!

Regards,

Louis
