Docker Deployment: How to provide credential to container?

[xtchall]

What I tried:

• attempted a local Docker deployment following https://github.com/ArcadeAI/arcade-ai/tree/main/docker
  (default Google auth provider enabled, Gmail API client ID and client secret in .env)
• curl http://localhost:9099/v1/health returned: { "healthy": "true" }
• browsed to http://localhost:9099/dashboard, Arcade dashboard does not load (error provided below)
• attempted running CLI arcade login so as to obtain credentials

What I wanted to do:

• open a browser and navigate to http://localhost:9099/dashboard to view the Arcade dashboard
• Arcade Docker deployment documentation: "NOTE: arcade login will not work within a docker container, you must copy your credentials into the container if you would like to use it."
• obtain credential and copy into container

Where I ran into problems:

• the following error results when attempting to load the Dashboard in a browser:

Something went wrong - Wrong assertion encountered: You must use useOidc inside the corresponding OidcProvider

• CLI arcade login ran without error but did not provide credential

System information:

• Intel Mac on macOS Sonoma 14.7
• Docker Desktop with Docker Compose

Would appreciate thoughts on:

• how to use CLI "arcade login" to provide credential to container, or
• how to use Oidc inside the corresponding OidcProvider

[evantahler]

Hello @xtchall - we just released a new version of our engine that should make it more clear that you'll need to contact support @ arcade.dev to obtain a key to use the engine locally (the engine is not OSS). This is a temporary limitation - we are building automatic registration into the engine shortly.

We can also start a thread about building tools with OIDC separately

[xtchall]

contacted support ([email protected]) to obtain a key to use the engine locally on Docker, several days ago and have not received a response

[xtchall]

“just released a new version of our engine” . . . Really? Where? Because all I see is the painfully lacking discussion at: https://docs.arcade.dev/home/local-deployment/install/dockerAlso do you have another suggestion as to obtaining the elusive local engine key for Docker deployments, as ***@***.*** does not respond to requests for a key. Actually, they don’t respond at all!Thanks for all your help. On Aug 21, 2025, at 5:04 PM, Evan Tahler ***@***.***> wrote: Hello @xtchall - we just released a new version of our engine that should make it more clear that you'll need to contact support @ arcade.dev to obtain a key to use the engine locally (the engine is not OSS). We can also start a thread about building tools with OIDC separately —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>