[{"data":1,"prerenderedAt":91},["ShallowReactive",2],{"blog-docker-desktop":3,"blog-docker-desktop-favor-of":50},{"id":4,"title":5,"body":6,"cover_image":27,"date":28,"decidedDate":28,"decision":29,"decisionInFavorOf":30,"decisionReason":31,"description":32,"evaluatedScore":33,"extension":34,"link":27,"logoPath":27,"meta":35,"navigation":36,"path":37,"placements":38,"reviewTrigger":27,"satisfaction":27,"seo":42,"stage":43,"stem":44,"tags":45,"target":27,"type":48,"__hash__":49},"radar\u002Fradar\u002Fdocker-desktop.md","Docker Desktop",{"type":7,"value":8,"toc":23},"minimark",[9,13],[10,11,5],"h1",{"id":12},"docker-desktop",[14,15,16,17,22],"p",{},"Rejected in favor of ",[18,19,21],"a",{"href":20},"\u002Fblog\u002Francher-desktop","Rancher Desktop",". Docker Desktop worked, but updates were a recurring pain point: errors that were hard to track down, sometimes forcing a full clean of containers and volumes just to get back to a working state. That's a hard thing to build confidence back from, even if it's more stable today than it was.",{"title":24,"searchDepth":25,"depth":25,"links":26},"",2,[],null,"2026-08-08","reject","rancher-desktop","Rejected in favor of Rancher Desktop. Simplicity and stability tipped it: repeated, hard-to-fix errors around Docker Desktop updates — sometimes requiring a full wipe of containers and volumes to start over — was unacceptable for a daily-driver tool. It may well be better now, but the confidence never fully came back.","Local container runtime and GUI for Docker, rejected in favor of Rancher Desktop.",4,"md",{},true,"\u002Fradar\u002Fdocker-desktop",[39],{"category":40,"subCategory":41},"tools","development",{"title":5,"description":32},"trial","radar\u002Fdocker-desktop",[46,41,47],"docker","containers","tech_report","YxZ9bjix0ZNKbiyeDXeupD9RFTBp7faZCZeesl059bw",{"id":51,"title":21,"body":52,"cover_image":27,"date":28,"decidedDate":28,"decision":78,"decisionInFavorOf":27,"decisionReason":79,"description":80,"evaluatedScore":33,"extension":34,"link":27,"logoPath":27,"meta":81,"navigation":36,"path":82,"placements":83,"reviewTrigger":27,"satisfaction":27,"seo":85,"stage":43,"stem":86,"tags":87,"target":27,"type":48,"__hash__":90},"radar\u002Fradar\u002Francher-desktop.md",{"type":7,"value":53,"toc":76},[54,56,68],[10,55,21],{"id":30},[14,57,58,59,62,63,67],{},"Adopted in favor of ",[18,60,5],{"href":61},"\u002Fblog\u002Fdocker-desktop",". Rock solid, simple, and focused mainly on Kubernetes — which matters since ",[18,64,66],{"href":65},"\u002Fblog\u002Fkubernetes","Kubernetes"," is already part of the adopted stack. No update-related breakage, no need to wipe containers and volumes and start over.",[14,69,70,71,75],{},"The local development split: ",[18,72,74],{"href":73},"\u002Fblog\u002Fdocker-compose","Docker Compose"," covers simple, low-complexity multi-container setups. Rancher Desktop takes over as the local Kubernetes toolkit once a project's needs get more advanced and closer to production topology.",{"title":24,"searchDepth":25,"depth":25,"links":77},[],"adopt","Adopted in favor of Docker Desktop. Rock solid and simple, with no update-related breakage or need to nuke and rebuild the local environment. It also focuses primarily on Kubernetes, which matters since Kubernetes is already an adopted technology here.","Local Kubernetes and container runtime for development, adopted in favor of Docker Desktop.",{},"\u002Fradar\u002Francher-desktop",[84],{"category":40,"subCategory":41},{"title":21,"description":80},"radar\u002Francher-desktop",[88,89,41,47],"rancher","kubernetes","ohiVMnGOf9NuMdA1z82vCjgt5caaJ8OVpldY_OF8pI0",1790263543287]