Thanks for reaching out! I wanted to share that the LiveKit CLI doesn’t currently support specifying a custom Dockerfile path directly with a flag like

--dockerfile_path

. The CLI looks for the

Dockerfile

in the working directory where you run the

lk agent deploy

command. If it doesn’t find one, no worries—it will generate a Dockerfile automatically for you. If you’d like to use a custom Dockerfile path, here are a couple of friendly workarounds you can try: • Copy or symlink the Dockerfile: Simply copy your custom Dockerfile into the directory you plan to use with the

lk agent deploy

command. For example:

cp ./build/Dockerfile.agent ./Dockerfile
lk agent deploy .

• Use a subdirectory as the deploy context: You can also place your custom Dockerfile inside a subdirectory and then point the CLI to that directory like this:

lk agent deploy ./deploy-voice

These approaches help make sure your Dockerfile is exactly where the CLI expects it—right at the root of your build context. If you have any other questions or need a hand with this, feel free to ask. I’m here to help! Sources: cmd/lk/agent.go | Agent deployment CLI reference | LiveKit Docs | Builds and Dockerfiles | LiveKit Docs | Deploying to production | LiveKit Docs | Voice AI quickstart | LiveKit Docs