Develop an external integration with a local Docker image

Hi.

I’m currently developing an external integration. I want to test my Docker integration image, but initially without wanting to publish it. The problem with developer mode is that it requires the image to be published on a Docker repository.

Here is the error:

2026-08-08T05:53:07.708837062Z 2026-08-08T07:53:07+0200 <warn> externalIntegration.install.js:44 (ExternalIntegration.install) Unable to pull image gladys-enphase:0.1.0 Error: (HTTP code 404) unexpected - pull access denied for gladys-enphase, repository does not exist or may require 'docker login' 
2026-08-08T05:53:07.708970278Z     at /src/server/node_modules/docker-modem/lib/modem.js:336:17
2026-08-08T05:53:07.709059009Z     at IncomingMessage.<anonymous> (/src/server/node_modules/docker-modem/lib/modem.js:363:9)
2026-08-08T05:53:07.709083833Z     at IncomingMessage.emit (node:events:531:35)
2026-08-08T05:53:07.709102097Z     at endReadableNT (node:internal/streams/readable:1698:12)
2026-08-08T05:53:07.709119958Z     at processTicksAndRejections (node:internal/process/task_queues:89:21) {
2026-08-08T05:53:07.709137978Z   reason: undefined,
2026-08-08T05:53:07.709154923Z   statusCode: 404,
2026-08-08T05:53:07.709256306Z   json: null
2026-08-08T05:53:07.709279427Z }

My image « gladys-enphase:0.1.0 » is local on my test machine. One idea would be to use « ./gladys-enphase:0.1.0 » to force the use of the local version or add an option to skip the pull step.

Thanks.

Hi,

You can definitely use GitHub to test and that’s what I do on my side. :wink:

For your first version, you don’t put the topic « gladys-assistant-integration » and you merge everything into main and you use in actions « Build and publish image » by selecting main.

Once you have the topic « gladys-assistant-integration » in place with your first version in place, you don’t merge into main and you use in actions « Build and publish image » by selecting the branch you are working on.

Once that’s done, you will have the instructions to test in both cases.

If it’s not clear, don’t hesitate :wink:

Ben that’s exactly what I want to avoid — creating a GitHub project just for this when I ultimately want to use GitLab.

Oh ok, I’ll let @pierre-gilles answer then :wink: