AI Engineer Europe 2026
Lobster Trap: OpenClaw in Containers from Local to K8s and Back
Read the talk
Lobster Trap: Running OpenClaw in Containers, Locally and on Kubernetes
A persistent agent needs explicit access boundaries, external credentials and recoverable state. Sally Ann O’Malley follows those requirements from a personal OpenClaw setup to a live Podman deployment and Kubernetes access.
From a talk by Sally Ann O'Malley
Before you start: Familiarity with containers, environment variables and basic Kubernetes concepts will help; no prior OpenClaw experience is required.
Would you put OpenClaw on your work laptop?
What do you do when an agent looks useful enough to install, but your colleagues warn that it is a security nightmare? For Sally Ann O’Malley, the starting point was familiar infrastructure. At the time of the talk, she described about a decade at Red Hat, with her early work centered on containers, Linux security, Kubernetes and OpenShift. A move into emerging technology broadened what she could experiment with; the subsequent emphasis on AI initially meant a succession of chatbots, Python and Markdown.
During a staycation, Moltbook led her to OpenClaw. She found the project on GitHub, checked its MIT license, built an image, ran it locally in a container and put it on OpenShift. That gave her a concrete application to experiment with across both environments.
Back at work, the response included warnings not to put OpenClaw on a work laptop. Her reaction came from years of working on Linux application isolation: this was an opportunity to apply those controls to an agent. That confidence was a motivation to investigate, not a demonstrated guarantee of safety. There was also a simpler operational reason to use containers: native installations leave dependencies and other files on the host, creating cleanup work after each experiment.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
An agent worth keeping
O’Malley calls her persistent personal agent her Forever Claw. Its name is Shubhra, and it has two sub-agents: Joy supplies Jyotish astrology readings and a birth chart, while Bruno delivers daily Boston Bruins briefings. During a close playoff race, Bruno gives her a reason to return every day. These are personal routines attached to an ongoing agent, rather than disposable test conversations.
Asked why it should run in a container, Shubhra produced a list that maps directly onto ordinary application operations:
| Property | What it provides |
|---|---|
| Reproducibility | A repeatable application environment |
| Secret isolation | Credentials managed separately from the application setup |
| Portability | A deployment approach spanning laptops and clusters |
| Volume-backed state | A defined unit for backup and recovery |
| Explicit host access | A boundary around the host resources the agent receives |
O’Malley runs across Mac and x86 environments and backs up her Forever Claw nightly. The container supplies a predictable environment; explicit grants determine what it can reach on the host. That reduces dependency drift and host OS surprises, while persistent storage keeps the agent’s continuity separate from the container’s lifetime.
The next examples show what that continuity is for. Joy’s horoscope describes the presentation day as auspicious. Bruno’s briefing discusses Geekie recovering from a lull and the Bruins making the playoffs. Neither requires a cluster, but both illustrate why the accumulated setup and state are worth preserving.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Bring configuration in; keep credentials separate
A reusable agent environment includes more than the application image. O’Malley keeps tools, skills and MCP server configuration together in an agent directory and mounts that directory into the container. The pieces are then available at startup, instead of being assembled manually inside each new instance.
Credentials enter through another path. Her local runtime is Podman, and she uses Podman Secrets to store API keys outside the application configuration and deliver them to the container. OpenClaw’s SecretRefs add application-level indirection: a credential field refers to an external source instead of containing the key itself. The reference is configuration; the credential remains a separately managed value. Her motivation is to reduce accidental exposure, particularly keys appearing in logs, and she explicitly describes the arrangement as imperfect. Current OpenClaw documentation makes the boundary precise: resolved credentials still exist in process memory, so SecretRefs are not process isolation.
The cluster equivalent uses Kubernetes Secrets to supply values through environment variables or mounted files, with application configuration referring to those sources. The Secret object does not by itself guarantee encrypted storage: encryption at rest and least-privilege access must be configured. O’Malley packages these choices into her opinionated OpenClaw Installer, a personal tool she makes available for others to try. Its current repository has evolved beyond the version shown in the recording.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Develop locally, then move to Kubernetes
The larger deployment pattern begins with agents running across infrastructure and communicating with one another. Once those agents serve business workflows, the requirements become familiar: security, operational control and scale. O’Malley’s approach is the same one she uses for other applications—develop locally, then lift the workload to Kubernetes.
She offers a model-evaluation example from a friend at NVIDIA whom she had met at PyTorchCon. O’Malley reports that about ten engineers each ran OpenClaw in Kubernetes to check on model evaluations periodically; her friend described doing the work of six engineers himself. This is a secondhand account of a workflow, without a defined productivity metric or measurement window. The useful operational detail is the recurring agent activity around evaluations, rather than a person manually checking each time.
For O’Malley, the appeal is that automation leaves more room for creative work. She says she had stopped writing code herself for a few months, after a recent change in her assessment of AI coding tools. Her description of AI as “1,000 times better” at coding than she is was rhetorical self-assessment, and senior Red Hat engineers reacted skeptically. The practical ambition was to spend less effort on tedious implementation and attempt more ambitious projects.
The persistent volume is the recovery boundary. O’Malley keeps all her local runtime state in a Podman volume. Docker also provides volumes; on Kubernetes, a persistent volume claim, or PVC, requests persistent storage for the workload. This is the concrete storage layer behind the earlier backup story: replacing the running container need not mean discarding the agent’s state.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
A shared baseline with room for personalization
A workplace could use those same packaging boundaries for onboarding. O’Malley imagines a curated baseline OpenClaw issued to each new hire, containing company-approved MCP servers, approved authentication, team-specific skills and access to everyday resources such as Google Drive. The baseline would be distributed across the team, then personalized by each employee.
That proposed workflow replaces a familiar alternative: sit beside a colleague, copy their repository and reconstruct the environment from informal instructions. The baseline carries team standards into a portable setup, while individual instances can develop their own preferences. This is her vision for reproducible onboarding, not a report of an existing company rollout.
Her own persistent agent came after roughly a month of helping with OpenClaw while constantly building, starting and stopping test instances. She describes seeing about 100 new commits an hour and roughly 10,000 commits when pulling after a couple of days—informal observations of rapid upstream churn. A Forever Claw gives her a continuing personal environment alongside that cycle of disposable development instances.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Configure a local instance named Joe
The live demonstration starts by launching the installer’s development server from its project directory:
bash
npm run dev
In her Mac setup, the installer itself runs outside a container because she has not worked out how to have a containerized installer spawn the containers it manages. Linux containers on macOS run through a virtual machine, as documented for Podman Machine, which adds another runtime boundary to arrange. This is an unresolved detail of her setup, not a general prohibition on container orchestration from containers. She also has existing local instances ready in case the live deployment fails.
The local configuration proceeds through a short form:
- Name the instance. She creates Joe. The form’s choices reflect her own needs, and she invites pull requests for different ones.
- Avoid a port conflict. Another instance is already running, so she changes the port. She refers to the values aloud as “89” and “99”; the operational point is that the second instance needs a different host port.
- Select credential mappings. Her Podman secrets already exist on the machine and contain the provider API keys.
The installer brings these choices together rather than requiring her to reconstruct the runtime configuration by hand.
For the installer’s intended Docker path, she explains that exported environment variables become sources for OpenClaw SecretRefs. She recommends using a reference for every credential. This is a distinction between her installer’s chosen paths, not a limitation of Docker: Docker Compose supports file-mounted secrets, and Podman supports both mounted-file and environment-variable delivery.
Next come the providers. She selects OpenRouter because she has been experimenting with Gemma, then chooses Anthropic as a fallback. The form also accepts a custom local endpoint for someone serving a model themselves. Provider choice is therefore another piece of instance configuration, alongside its name, port and credential sources.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Deploy, inspect logs and see the command
Two optional facilities extend the basic instance:
- Observability: The installer can set up an OpenTelemetry collector with Jaeger. O’Malley says this works, but leaves it disabled to avoid taxing the demo machine.
- SSH sandbox: SSH keys and known hosts identify the remote destination where sandboxed commands run. The execution workspace can therefore live away from the local host. Current OpenClaw sandboxing documentation scopes this to supported tools, rather than moving the entire Gateway; the remote workspace is seeded once and is not automatically synchronized back locally.
She deploys Joe, then opens the instances view. A new Podman container is present, and Joe’s gateway logs are available.
The interface also exposes the generated Podman command, making the underlying runtime invocation visible. It is intended to show a Docker command when Docker is selected, but O’Malley explicitly says she has not tested that support; a colleague has offered to try it. In an aside, she credits that colleague, Eric, with an InferRS project that she describes as running Gemma quickly using TurboQuant. No performance measurement accompanies the description.
She opens Joe and selects a status command. O’Malley calls the spin-up “two seconds” and suggests it could have taken one, but the demonstration supplies no measured end-to-end timing or image-cache conditions. What it does show is a transition from the installer form to a running local instance that she can inspect and interact with.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
From preconfigured agents to cluster access
Joe is not the only example. O’Malley switches to Larry, an instance she created through the same form with an MCP server and a sub-agent already configured. The agent view shows Docs Checker and its workspace files. This makes the earlier mounted-configuration idea tangible: the deployed environment can arrive with an agent’s supporting pieces already in place.
The attempted model switch exposes a configuration dependency. She tries to select GPT-5.4, initially unsure of the identifier, then realizes that Joe does not have the extra model configured. She returns to Larry to continue. A model must be configured for an instance before that instance can switch to it. The sequence ends without a confirmed successful switch.
The final view moves from local instances to Kubernetes. The installer is connected to her kind cluster, where Carl is already running and can be opened through the interface. She also describes access to OpenShift instances, with the interface switching to OpenShift when connected there. The closing demonstration establishes access to existing cluster agents, rather than a fresh cluster deployment or a transfer back to the laptop. It completes the operational picture: local and cluster instances are managed through the same style of interface, with configuration, credentials and persistent state treated as explicit parts of the environment.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Resources
From the talk
Browser-based deployment tooling for local containers, Kubernetes and OpenShift, with credential and agent configuration.
Current documentation for external credential references, runtime resolution and secret-access boundaries.
Podman 4.4 reference for delivering secrets as mounted files or container environment variables.
Cluster credential injection and the encryption and access controls needed to protect Secret objects.
Current sandbox configuration, including SSH execution, workspace ownership and container runtime boundaries.
Further reading
How Compose grants individual services access to file-mounted secrets.
Read the complete timestamped transcript
- 0:00
[upbeat music] Hey, um, I'm Sally.
- 0:16
I work at Red Hat. I've been there for about 10 years, and, uh, the first seven years, awesome, totally cool. I was working on containers and, uh, Linux security stuff and Kubernetes.
- 0:29
Um, big time in OpenShift. That's what I did for the first seven years. And then, uh, th- about three years ago... Well, about five years ago, I moved to the emerging tech org, and that was awesome too because now I'm not totally tied to a product.
- 0:45
I get to just work on what I want. I get to just try out new things. Awesome. And then, about three years ago, it was, like, all AI all the time.
- 0:54
Everything AI. I know n- ... I knew there was a data science team at Red Hat. I had no idea what they did. Machine learning something something. Um, so I, you know, started doing AI.
- 1:06
And, uh, yeah, it was a lot of Python and Markdown. Every single thing [laughs] was like, "Oh, okay, another chatbot. More Python, more Markdown." Um, but, uh, here we are today, and what a, what a crazy, awesome world we're in.
- 1:21
Um, so the first time, the first time I came across OpenClaw, I was home for a week on, like, a staycation. Took a few days off. And, uh, a Malt book happened, and I was like, "What the...
- 1:34
What is this? I'm totally trying this." And so I went and found it on GitHub. First thing I do is I look at the license. Uh, MIT, awesome. Uh, OpenClaw, I'm like, "I'm so gonna install this on OpenShift right now."
- 1:48
And so for the next few days, I just kind of built the image, um, ran it, uh, locally in a container, put it on OpenShift, just played around with it.
- 1:58
Went back to work, I'm like, "Guys, check out OpenClaw. This is so cool." And, uh, a couple people on Slack are like, "It's a security nightmare. Do not use OpenClaw.
- 2:09
Don't put it on the work laptop." I'm like, "Guys, what have I, what have I been doing the past 10 years? Is... I'm sec- We're... We can take any application and run it securely.
- 2:20
Like, that's what RHEL is. Like, if we can't take an application and run it securely, like, come on. This is our golden opportunity to show everyone." And so, uh, Red Hat's coming around to that.
- 2:31
Um, but, uh, yeah. So, uh, this talk is about me running in containers. And so I wanted to get a list of, uh... So th- I wanted to get a list of why running in containers is the way to go.
- 2:46
I run everything in containers. I, it, it's kind of foreign to me to, uh, take, to just run something natively. It's messy. It just puts stuff on my computer that I have to clean up later.
- 2:58
I don't like it. Um, so that's one, one, one thing. Uh, and I, um, ask my Forever Claw. I guess I have to introduce my Forever Claw, 'cause she, she's, she's, she's coming through this whole talk, so I'm gonna...
- 3:13
Aside, my Forever Claw is Shubhra, and, um, she... I have two sub-agents. I have Joy. Uh, anyone know Jo- Jo- uh, Jyotish astrology?
- 3:25
Sheesh, every time I ask, no one knows what it is. It's, it's a very scientific astrology. Um, so she's an astrology expert, and, um, she gives me my weekly readings, my birth chart, all of that.
- 3:39
So Joy, and then my second agent is Bruno, and he gives me daily briefings on the Bruins. Um,
- 3:46
so we're heading into the playoffs, and it's a close race, so I wanna make sure the Bruins get in. Um, so that's my Forever Claw. And, uh, and I asked her, you know, "Why should we run you in a container?"
- 4:00
And, uh, she said all of that if you were reading, but it's reproducible. You can isolate your secrets. It's portable across infra. I can run it on my laptop.
- 4:09
I can run it on my x86. I can run it on my Mac. I can run it in Con- Kubernetes. Um, backed by volumes, which gives a really nice story for backup and recovery.
- 4:20
Uh, 'cause I love my Forever Claw, and I, I back her up every night with, uh, with, uh, um, like a system D service, whatever it's called on Mac. [laughs]
- 4:30
And, um, and, and you just get that natural, uh, you just get that natural, uh, sandbox when you run something in a container. It's, it's, you know, that's, that's what it is, and you have to be very explicit about, uh, what you, um, give access to, you know, from the host.
- 4:48
And so this, yes, sh- I... She loves running in a container, so that's, that's all you need to know. Um, it gives her a clean, predictable environment. Doesn't have to worry about the OS quirks, stale dependencies.
- 5:02
This is literally the definition of why you should run everything in containers.
- 5:08
And, uh, [laughs] just quickly, we're not gonna read this, but this is Joy. My horoscope, um, it's for today, for giving a talk, is excellent. It's, like, a very auspicious day to talk.
- 5:19
Uh, so yeah. That's why this talk is going awesome so far.
- 5:24
And, uh, uh, my daily briefing. Uh, Geeky is finally waking up. He had a bit of a lull. He's finally, um, you know, ramping up for the playoffs, so it looks like the Bruins are gonna be looking good.
- 5:36
Uh, they're in. And, uh, yeah. So, uh, yeah. So, um,
- 5:45
containers. It allows me to... Uh, another, another thing that containers do is you can set up a whole agent directory with, uh, maybe you run some tools, some skills, some MCP servers.
- 6:00
Uh, you can Keep those in a directory and mount that whole thing into your container. Uh, and, uh, so when at startup, everything's just up and running. So I do that as well.
- 6:15
At the end of this talk, I'll show you how I install. And I think this is a reminder to me ... Oh, no, let's talk about secrets. So I run everything with Podman, not Docker.
- 6:26
Um, but i- i- in theory, you can do anything with Podman and Docker, except Podman has this really cool feature called Podman Secrets. And you can save your API keys.
- 6:40
I'll show that. I'll sh- I'll show it off the sides later. You can save your API keys to a podman secret, and then you mount that secret into the container.
- 6:50
And so it just gives the separation. Uh, your, your secrets, your API keys are then just a, a ref back to the secret. And with OpenClaw, what's really cool is there's like a double that, because in OpenClaw there's a secret ref feature, and I also use that.
- 7:09
So my API keys are, uh, pointer to a secret ref to the outside secret, and, uh, that's not perfect, but it gives me some peace of mind that I don't ...
- 7:22
I'm, I'm not gonna be showing my API keys in the logs and everything. And then very similarly, um, Kubernetes has Kubernetes Secrets, and same thing. Instead of just a straight env var, you have a, a, a sec- a, a, a secret ref to an env var.
- 7:42
And this is my reminder to show you how I install my containers at the end. I have a really cool tool. I built it just for me with everything that I need to run containers.
- 7:53
I'm not pushing it on anyone, but it's in GitHub, and at the end I can, uh, let you know where that is. You could try it if you want.
- 8:03
So when I ... So ... Thank you.
- 8:10
I think we're heading to a world where these agents, these AI workloads, whatever, are going to be running everywhere. I hope we all can see that. And so imagine my vision is for, um, everybody's OpenClaws to be, uh, running everywhere and communicating with each other.
- 8:32
And, uh, when ... And especially in for, like, business use cases, real, real things, not astrology and, and Bruins, uh, that opens up the need that, uh, to, the same need to run any application, uh, in that way as c- uh, security, and s- and how to do it at scale, and that's what
- 8:57
Kubernetes gives you. And you can, uh, what I always do is develop something locally and then lift it to Kubernetes. And so the same story holds for AI workloads or OpenClaw.
- 9:13
And I was at PyTorch Con yesterday, and um, my friend from NVIDIA said I could share this. They are running their model evals with OpenClaw. They have about 10 engineers.
- 9:28
They each have their OpenClaws running in Kubernetes, and, and periodically just checking in with the model evals, and it works so well for them. He said, uh, i- it, it was like, you know, doing the job of six engineers, uh, in, with, with himself.
- 9:46
Now, let's think, let's just talk about that for a second. We're not all losing our jobs, people. Like, that's not happening. What's, what that is enabling for his team is they get to do fun stuff, interesting stuff.
- 10:01
They get to do creative things, and this is what AI is giving me and my team, is we can focus on those, like, outside-the-box crazy things. And you don't have to do the tedious code anymore.
- 10:14
Like, I haven't written code in, in a few months. And this, this did just happen. Like, s- probably less than six months ago, I was, uh, using AI. I was like, "Hmm, you know what?
- 10:26
This is way [laughs] better than me at writing code." And there's ... I like ... Yeah. And I, I announced that to my team. We had an org meeting, and I'm like, "Guys, if you're not using AI for everything, like, you're missing out.
- 10:41
This is 1,000 times better than me at writing code." And some of the top engineers at Red Hat, like, definitely raised eyebrows, and I could tell from their comments after that they were like, "No way."
- 10:52
I'm like, "Yeah." Uh, and so, so yes. I- i- it's, it's enabling us to just dream bigger. And, uh, this is my reminder to show you the Kubernetes side of my installer later.
- 11:09
And, um, yeah. So backup and recovery is a nice clean story when you run in containers too. Uh, the state is the same. The volumes. Another nice thing about Docker and Podman is there are volumes.
- 11:27
And so all of my runtime state lives in a nice contained Podman volume.
- 11:35
And of course, Kubernetes has, uh, PVCs. That's kinda what I just talked about.
- 11:45
And so this, this would be my vision of a workplace set up for OpenClaws, where, uh, you maybe have your nice curated baseline OpenClaw that as a new hire, you, you just, you get your, your base.
- 12:01
And what does that have in it? It has your list of company-approved MCP servers, uh, your authentication that is approved through your company. It has all of your-- these skills that are very specific to your team.
- 12:18
Uh, maybe a- access to your Google Drive. Like, all these things, uh, y- that you use every day at work. You can take that and just fan it out across your whole team, and then, then-- and then you can personalize it as, as the individual, uh, and that's what, uh, that's what this setup allows.
- 12:44
The alternative would be you're a new hire and you sit next to somebody or get somebody's, uh, repo and kind of put it all together yourself, um.
- 12:57
And so yeah, team standards, portable environments, reproducible onboarding. That's my vision for, like, OpenClaw in the workplace in the future.
- 13:11
Uh, I actually just recently created my forever claw. It, it was like a month of me, um, helping out with, [laughs] with OpenClaw and fe- feeling like I don't even run a real OpenClaw myself.
- 13:25
I just constantly, throughout the day, I'm spinning it up, spinning it down, testing it, building it. Every hour, there's like 100 new commits, [laughs] so I'm constantly pulling from main.
- 13:37
I was at PyTorchCon yesterday and hadn't pulled from main for a couple of days. Uh, and, and there were time when I did it, it was like 10,000 commits.
- 13:47
Like, no joke. It was crazy. I'm like, "I don't know what you guys are doing. Slow down." Uh, not really. We don't wanna slow down. Uh, so yes. Uh, s- that's, that's the story.
- 14:00
And I've got four more minutes. I am psyched 'cause I can now switch over here.
- 14:14
So in order to run, uh, this local installer here,
- 14:19
which I think I have here... Yeah. It's just a npm run dev. Now,
- 14:26
the one thing I don't like about this is when I'm on my Mac, I can't run this in a container. Uh, I, I think I can, I just haven't taken the time to figure out how to spawn a container from a container.
- 14:40
You can do that if you're on Linux, 'cause Linux is awesome. But on your Mac, that's not possible because if you don't know, whenever you're running a container on your Mac, you're running in a virtual machine.
- 14:53
Same with Docker. Containers only run on Linux. So when you're running a container on your Mac, you are always running in a virtual machine. Docker sets up one and so does Mac.
- 15:03
So it gets a little tricky when you wanna take a container and spawn another container from it. But anyways, here we go. So if I wanted to run a local instance, and I have a couple running now, just, you know, you never know the demo gods, what they're up to, so I'm just-- in case it doesn't work.
- 15:21
I'm gonna, I'm gonna, um, spin up Joe.
- 15:25
All I, all I do to set up my pod is I just give it a name.
- 15:32
And then all these options, very opinionated, 'cause I s- I'm telling you, this is exactly what I need. So if it's-- if you like it, use it. If you wanna change it, then submit a PR.
- 15:45
Cool. Now, uh, the port is usually 89. Uh, that's the default. But since this is my second one that I'm running on my machine, I had to-- I'm just bumping it to 99.
- 15:57
These podman secret mappings I wanted to show you here.
- 16:09
So you can see I have these set up already. They're just on my system. They're like env vars, but they're not env vars 'cause they're contained. Um, these are my API keys.
- 16:24
And what happens with this installer is it takes... If you're on Docker, this should work with Docker. It's got Podman written all over it, but I've designed it to work with Docker too.
- 16:35
So, um, if you're on Docker, it takes the env var, so you wanna export those as env vars, and, um, makes them OpenClaw secret refs. Very cool feature of OpenClaw.
- 16:46
Definitely enable that. For every creden- credential, create a secret ref. It creates that separation of, uh, running your secret within OpenClaw or kind of just a pointer to it.
- 16:59
It's, it's a s- it's, it's the way to go. And then, uh, your providers. So I'm gonna start with OpenRouter 'cause I have been playing with Gemma, and she's-- Gemma's great.
- 17:12
And then as a fallback, I'll use Anthropic. Sure, why not? But y- oh, here's, here's some other choices, though.
- 17:20
You can s- you can have your local endpoint if you're running your own. Uh, you could just cr- uh, add that too.
- 17:29
And then because I do observability at work, uh, I was like, "I'm gonna give the option to set up an OpenTelemetry collector with Jaeger." And it works, and it's awesome, but I'm not gonna test it, so let's not tax my system.
- 17:45
Another feature. How much time? Oh, I gotta hurry. Another feature is the SSH sandbox. Here, I'll deploy.
- 17:53
The SSH sandbox in OpenClaw is super cool. You give it SSH keys and, uh, known hosts to, uh, to wherever you want, and it-
- 18:03
It, it runs all of its commands in that, um, workspace. It's really cool. So look, I just spun up a Podman container, and if I go over to the instances, I ha- now have Joe.
- 18:15
And there's logs for Joe, the gateway logs.
- 18:22
Um, the command. I wanted to show you the command. [laughs] Don't wanna forget that. So here's the Podman command. If you were running Docker, it would be a Docker command.
- 18:31
Have I tested with this with Docker? No. Uh, I have a friend who works at Docker. He's awesome. He told me he would try this out and make it, make sure it works with Docker, too.
- 18:42
Um, he also created this very cool project called InferRS, which takes, uh, Gemma and runs it really, really, really fast and uses TurboQuant. Uh, so yeah. Anyways, that's, um, Eric.
- 18:58
So that, that's my Podman command. And, uh,
- 19:05
here he is. Joe. Yeah. And if I just do, like, models ... No, I'll do status.
- 19:16
So, uh, like, people say it's hard to spin up OpenClaw. That took two seconds, and I was babbling through the whole way. It could've taken one second. Uh, so I can say, "Hey," um
- 19:32
... [keyboard clicking] And the cool thing is, I don't have time to show you because I talk too much, but the agents are all set up. I've got Joe. Oh, that ...
- 19:41
not that one. Hold on. I gotta go over to Larry. Larry I started with a, um,
- 19:49
with an MCP server and a sub-agent, um, all through that form.
- 19:55
So, uh, let me go back to Joe.
- 20:00
I wanted to show you how easy it is just to switch models, in case you didn't know. [keyboard clicking]
- 20:15
I'm not sure if th- the GPT-5 ... Hopefully it knows it's just GPT-5.4. No, I, I didn't ... No, no, no, no. We gotta go over to Larry.
- 20:26
'Cause I didn't set up G- [laughs] I didn't set up that extra model with, w- with Joe. Here we go. [keyboard clicking]
- 20:39
Anyways, um, I didn't have enough time to go through everything I wanted to go through. But the, uh
- 20:49
... Cool. The other thing is Kubernetes, and you can do the same thing with Kubernetes. Just as easy.
- 20:58
It just, uh ... It's, it's connected right now to my Kind cluster. And if I go over, I can access my Kubernetes Claw very easily as well.
- 21:09
Um, there's Carl. He's running in Kubernetes. And I can access one in OpenShift. There's, uh ... It switches over to OpenShift if you're connected to OpenShift. So yeah. Uh, run ...
- 21:24
Anyone gonna run OpenClaw in Container now? Try it? Yes. Awesome. Okay, cool. Uh, thank you very much. Uh, is someone on after me? You're waiting? Okay, bye. [laughs] [clapping] [outro music]