تستخدم الذكاء الاصطناعي داخل Docker Sandboxes؟ جدّد شهادات البيئات القائمة

Read this news or bug-fix article as reference material:
https://nethanelfitoussi.com/article/docker-sandboxes-october-2026-certificate-refresh?lang=en

Goal: apply the documented workflow to my development project.
Read the existing project instructions, inspect the relevant files and explain the smallest useful setup.

Use the article and its examples as references. Identify any missing project files before making changes.

If I have not supplied a project folder, ask which development project to use. Do not invent a repository URL.

Additional project setup instructions:
Using https://docs.docker.com/security/security-announcements/ and its October 21, 2026 Docker Sandboxes certificate guidance, inventory my existing sandboxes, template origins and bundled trust stores. Updating the sbx CLI alone does not update existing sandboxes. Prefer a documented non-destructive certificate update where suitable; for Ubuntu-based built-in templates Docker documents updating ca-certificates and restarting applications. If proposing recreation, first identify files and unpushed commits that must be exported, restore creation options and fetch updated templates with --pull always. Never run sbx rm or delete a sandbox without my explicit approval after preservation is verified. Also identify tools that bundle their own CA roots. Do not disable certificate verification or change production.

Check the dated advisory and current official vendor guidance. Identify whether my installed version and configuration are affected before proposing a fix.

Give me a short plan, then make the agreed local changes and run the relevant checks. Report actual results and anything not verified. Stop before credentials, paid services, production changes, push, merge or deployment.