tall-ability-51442
12/23/2025, 1:23 PMtall-airline-16756
12/23/2025, 1:23 PMtall-airline-16756
12/23/2025, 1:24 PMDockerfile and live in the project root. lk agent deploy looks for Dockerfile in the current directory and does not support passing a renamed file or custom path.
If you want, tell me your project layout and I can suggest how to move or generate the Dockerfile so deployment works.
Sources: Deploying to production | LiveKit Docs | livekit/livekit_composite | DeepWikitall-ability-51442
12/23/2025, 1:25 PMtall-airline-16756
12/23/2025, 1:25 PMlk agent deploy requires a file named Dockerfile in the directory you run it from, the typical approaches are:
• Keep the LiveKit service in its own subdirectory with its Dockerfile, then run cd path/to/livekit-service && lk agent deploy.
• Keep Dockerfiles next to each service and script the deploy step (CI job or local script) to cd into the correct service folder before running the CLI.
• If you prefer running from repo root, copy or symlink the service's Dockerfile to the root as Dockerfile before deploy (or have your build script do this).
Which setup are you using (separate service folders, CI pipelines, or running from root)? I can suggest a concrete script or CI example for your workflow.