404 using an engine that runs in a container with the VSC extension

konradWERTSCHOEPFER

Hi,

I'd like to develop with the VS Code extension (axonivy.vscode-designer-14, 14.0.34) but reuse an Axon Ivy Engine that already runs in a Docker container, instead of letting the extension download and manage its own engine.

My setup: a dev container based on axonivy/axonivy-engine:milestone-slim, with MS SQL Server as a second compose service, and my own ivy.yaml plus licence mounted into the engine's configuration/. The engine itself works — it starts up and connects to MSSQL.

The extension, however, always fails with a 404 at "Create Workspace"

I tried:

axonivy.engine.runByExtension: false 
axonivy.engine.url: http://localhost:8080

My actual question: what is the recommended way to set this up? I want one engine, running in a container, with my own configuration and database — and the extension working against it. Is that a supported scenario, and if so, which combination of settings and which engine distribution should I use? Or is the intended approach a different one entirely?

Any pointers from someone who has this running would be much appreciated.

Thanks!

Louis Müller

Hello,

The REST endpoints used during development, such as Create Workspace, are not available when running the engine in production mode. The engine must be running in demo mode to use these endpoints.

Therefore, I recommend sticking with:

"axonivy.engine.runByExtension": true

If you want to run your own engine, please run it in demo mode and set the following environment variable:

ENV JAVA_OPTS_IVY_SYSTEM="-Ddev.mode=true"