Leading sandboxes @Docker. @testcontainers maintainer, guitar & simracing, husband ❤ @taubenmaedel & dad
Gelsenkirchen
Joined January 2011
- Tweets23.9K
- Following1K
- Followers2.3K
- Likes30.2K
sbx coming to @testcontainers !
Hey! @testcontainers for #Golang has a new @Docker Sandboxes provider: one import plus TESTCONTAINERS_PROVIDER=sbx, and every container your tests start runs on the sandbox's own Engine. Test functions stay as they are. Feedback is always welcome 🙏
mdelapenya.xyz/posts/2026-10…
#golang #testcontainers #sbx
Kevin Wittek retweeted
@Docker meetup in Friburgo! 🤌
Many thanks to @mfranz_on for his great talk on token consumption tracking in #sbx. – at Merzhausen, Deutschland
Kevin Wittek retweeted
Siri is still bad, like really really bad. I opened an email with my Uber Eats confirmation, there was a live activity on the screen with progress, and I pulled down and asked Siri "what did I order for lunch?" And it thought for like 2 minutes and then said it doesn't know. 🤦♂️
Okay so the harness and models are clearly bad. Well, then next I opened up the Siri GUI app on macOS and HOLY. It's the worst looking, beginner, basic bitch app I've ever seen. Did someone spend more than 5 minutes on this?
Whoever worked on this app along with the full chain of people who checked off on this needs to be terminated immediately. This is 0/10 terrible software, so embarrassed for Apple to ship this.
Will work great in @Docker sbx.
Giving you the keys to the Lamborghini 🤓
Very good!
The coding interview is dead, at least for my team at Anthropic. I've seen enough to know that it no longer provides signal. I removed it from loops this month.
I have a spicy, optimistic take - I think there's an opportunity for junior engineers: felixrieseberg.com/hunger-be…
Kevin Wittek retweeted
Windows Copilot was so terrible it might very well have seeded the AI opposition we now see among normies. Useless functionality, hyped to the moon, and a dumb key on every keyboard that did nothing worthwhile. youtube.com/watch?v=erRVsllM…
Kevin Wittek retweeted
Containers became the standard by solving a specific problem: making software portable and reproducible. @TheFuturumGroup frames the Kit Spec as a continuation of that, for agent authority.
Full analysis: bit.ly/4echUM7
Funnily enough, I had my agent drive the latest sbx release pipeline through the end, by saying "babysit the pipeline" :D nitter.cf/Docker/status/21104768…
Don’t babysit your agents. Put them in sandboxes. Each sandbox is a microVM with its own kernel. And now they run in the cloud, too.
Ready to try it out? New signups get $250 in Cloud Sandboxes credit. Claim yours before the promotion ends on October 31: docker.com/c/sbx-promo/
Kevin Wittek retweeted
Bioware closure.
I’ve said before. It’s okay for a game company to go away. It’s happened to me several times. Companies mean nothing. It’s the people who matter, and a company closing doesn’t kill them. If they were awesome they will have a great resume and find a new, better job. If they sucked they can still find a good job - with luck not in the game industry.
We’ll always have Mass Effect and Baldur’s Gate anyway. And the people who built them will make something new and wonderful.
“Go for the eyes, Boo!”
We released the sbx patch release 0.49.2, to mitigate the eMudhra certificate incident:
github.com/docker/sbx-releas…
That makes me very sad :(
But honestly, I also wasn't really interested in their latest releases anymore...
BG and NWN were such big influences in my gaming life.
Kevin Wittek retweeted
As you've probably heard, eight intermediate CA certificates have been compromised due to dangerously weak private keys...
For those of you already patching your systems, don't forget about Docker Engine! (And almost everything else...)
docs.docker.com/engine/relea…
Yeah so this happened, yes? Latest ChatGPT/Codex desktop app release contains a bug, that means you can't submit messages? :D
github.com/openai/codex/issu…
Giving the new @claudeai projects beta a spin for some @testcontainers maintenance and it is a good UX spin, matches my way of working I guess.
Funny, how I initially didn't even notice that it would spawn cloud containers for each new thread.
support.claude.com/en/articl…
With the ping-pongy nature of AI code reviews, what is your merge strategy for PRs? Squash them to a single PR that makes sense, just merge as is, re-create sensible commits before merging?
