What is the best way to get docker in docker supported for background agents? I have pytests fixtures which leverage testcontainers to spin up services like clickhouse. I would like the background agent to be able to run these tests, but I cannot seem to get docker in docker working since I don’t see how to pass the privileged flag.
What is the recommended path for a devcontainer that supports docker test containers?
Thanks!
Not using docker to provision the background agent, AI can setup docker environment in the background agent.
There should be a way to do this with dockerfile too.
Been trying this too, was able to install Docker via the convenience script, but trying to run the daemon still fails:
The docs (Cursor – Background Agents) mention this though, so not sure what else needs to be done:
The
startcommand can often be skipped. One common case where you want to use it is if your dev environment relies on docker, in which case you would want to putsudo service docker startin thestartcommand.
I tried replicating this locally and the only way to avoid the “ulimit: error setting limit” error was to use --privileged and --ulimit nofile=65535:65535 like this:
docker run --privileged --ulimit nofile=65535:65535 -it test bash
I don’t think Cursor’s configuration file allows customizing these options though, so still not sure how to get this to work with background agents.
Did you end up figuring this one out? Figured out how to install docker & docker compose in the first place, but when running service docker start I’m getting the ulimit error you have above.
I have the same problem here. My tests depends on using testcontainers to spin-up two ephemeral databases and currently the background agent is unable to run tests. Installing the docker client is simple, but there should be a docker daemon running. Curious about an official solution.
there is a start option in environments json, so you can run docker start.
could you share an example?
Sure,
{
"snapshot": "POPULATED_FROM_SETTINGS",
"install": "npm install",
"start": "sudo service docker start",
"terminals": [
{
"name": "Run Next.js",
"command": "npm run dev"
},
{
"name": "Watch Files",
"command": "npm run watch"
}
]
}
When I do this, I get
/etc/init.d/docker: No such file or directory
docker: unrecognized service
hi @Dan_Claroni this is because you are trying to use a Docker based MCP which requires the installation of docker (another software to run the MCP you want).
Hi everyone. I have a short example that demonstrates Docker-in-Docker working, so I’d like to share it. This gets the Docker daemon running when the task starts, but when I attempted to launch containers in the terminals, they were ignored
FROM ubuntu:25.04
ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get update && apt-get install -y \
sudo \
curl \
wget \
ca-certificates \
gnupg \
lsb-release \
&& rm -rf /var/lib/apt/lists/*
RUN mkdir -p /etc/apt/keyrings && \
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | gpg --dearmor -o /etc/apt/keyrings/docker.gpg
RUN echo \
"deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu \
$(lsb_release -cs) stable" | tee /etc/apt/sources.list.d/docker.list > /dev/null
RUN apt-get update && apt-get install -y \
docker-ce \
docker-ce-cli \
containerd.io \
docker-buildx-plugin \
docker-compose-plugin \
&& rm -rf /var/lib/apt/lists/*
RUN groupadd -f docker
RUN usermod -g docker -G sudo,ubuntu ubuntu && \
echo "ubuntu ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers
WORKDIR /workspace
USER ubuntu
VOLUME /var/lib/docker
CMD ["/bin/bash"]
{
"build": {
"context": ".",
"dockerfile": "Dockerfile"
},
"start": "sudo service docker start",
"terminals": [
{
"name": "Run Nginx",
"command": "docker run -p 8080:80 nginx"
}
]
}