getting an error when using lk agent create: lk ag...
# ask-ai
p
getting an error when using lk agent create: lk agent create Using project [convos] project does not match agent subdomain [convos]
t
Thanks for reaching out, adit-kulkarni. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
Thanks — I’m responding about the error you saw when running `lk agent create`: "project does not match agent subdomain [convos]". Please try these steps and tell me what output you get or where it fails: 1. Confirm which project the CLI is using: ◦ Run:
lk project list
◦ Tell me which project is marked default. 1. If the default isn’t
convos
, set it: ◦ Run:
lk project set-default "convos"
1. Check your local agent config: ◦ Open
livekit.toml
and confirm the subdomain under
[project]
is:
Copy code
[project]
     subdomain = "convos"
1. Re-authenticate if things still look correct: ◦ Run:
lk cloud auth
1. Re-run the create command and capture full output: ◦
lk agent create
◦ If it fails again, paste the exact command output and the first 20 lines of
livekit.toml
(remove any secrets). If you prefer, tell me: • the output of
lk project list
, and • the
[project]
section from your
livekit.toml
. I’ll guide the next steps once I see those. Sources: Deploying to production | LiveKit Docs | Examples | livekit/livekit_composite | DeepWiki
p
ok it worked when i regenerated the toml file. but when i run lk agent create i get an error, but despite this i still see the agent in my dashboard lk agent create Using default project [convos] Creating new agent Using secrets file [.env.local] Detected project type [python.uv] Using existing Dockerfile Using existing .dockerignore [+] Building 4.7s (9/10) => [internal] load remote build context 0.5s => copy /context / 0.0s => [internal] load metadata for docker.io/library/python:3.11-slim 0.3s => [1/7] FROM docker.io/library/python:3.11-slim@sha256:158caf0e080e2cd74ef2879ed3c4e697792ee65251c8208b7afb56683c32ea6c 0.0s => => resolve docker.io/library/python:3.11-slim@sha256:158caf0e080e2cd74ef2879ed3c4e697792ee65251c8208b7afb56683c32ea6c 0.0s => CACHED [2/7] WORKDIR /app 0.0s => [3/7] RUN pip install uv 2.8s => [4/7] COPY pyproject.toml . 0.0s => [5/7] COPY src/ src/ 0.0s => ERROR [6/7] RUN uv sync --frozen --no-dev 0.2s ------ > [6/7] RUN uv sync --frozen --no-dev: 0.169 Using CPython 3.11.14 interpreter at: /usr/local/bin/python3 0.169 Creating virtual environment at: .venv 0.172 error: Unable to find lockfile at
uv.lock
. To create a lockfile, run
uv lock
or
uv sync
. ------ unable to create agent: build failed for fra.ocir.io/axyci3pr8vxm/production-cloud-agents:p-618g63lhei5-ca-omtdg4ucqztx-v20251227113901: failed to solve: process "/bin/sh -c uv sync --frozen --no-dev" did not complete successfully: exit code: 2
t
Thanks — I’m responding about the build error you see when running
lk agent create
(error: "Unable to find lockfile at `uv.lock`"). What happened: the CLI detected a Python/uv project and the Dockerfile runs
uv sync --frozen --no-dev
. The
--frozen
mode requires an existing `uv.lock`; without it the build fails even though the agent record was created in the dashboard. To fix this: 1. Generate the lockfile locally: ◦ Run:
uv sync
◦ Or:
uv lock
1. Confirm
uv.lock
appears next to
pyproject.toml
in your project root. 2. (Optional but recommended) Add
uv.lock
to version control so future builds are deterministic. 3. Re-run the create command: ◦
lk agent create
If it fails again, please paste: • The full output of
uv sync
• The first ~30 lines of
pyproject.toml
• The Docker build error (if different) I’ll help you from there. Sources: Agents (Python) | livekit/livekit_composite | DeepWiki | Examples | livekit/livekit_composite | DeepWiki