Docker per session
Allow Docker for a desktop thread, take it back, and fix a thread that needs Docker when it isn't running.
On this page
Docker access is a separate permission, asked once per thread, because Docker can reach well beyond one folder. Ysra asks the first time a command in a thread needs it. This page covers the question, what it allows, and taking it back.
Asked once per thread.
The rule#
Docker is allowed for one thread’s session at a time, only by you: “Only this session. Auto mode never answers this. You can revoke it any time.”
What each answer does#
| Answer | What happens |
|---|---|
| Allow for this session | Ysra’s commands in this thread may use Docker until the session ends. A new thread asks again |
| Not now | Ysra carries on without Docker where it can. Say “continue” if you change your mind |
Ysra never uses your Docker registry sign-ins: commands get an empty Docker configuration of their own.
Take it back#
While it’s allowed, the top of the thread shows Docker: allowed for this session with Revoke beside it.
Revoke at any time.
After you revoke it, the thread says Docker is off for this session. I’ll ask again if a command needs it.
When Docker isn’t running#
| You see | What to do |
|---|---|
| A Start Docker? card | Go ahead, or start Docker yourself. See Machine setup |
Related#
- Approvals and auto mode: what else asks once per thread.
- Machine setup: starting or installing Docker.
- Troubleshooting: when Docker is blocked.

