YueGuobin ce90b2b92c fix(docker): handle container name conflict automatically
When a Docker container with the same name already exists (e.g., from a
   previous crashed GNS3 session), Docker returns a 409 Conflict error
   when trying to create a new container with that name. This causes the
   project open operation to fail.

   This fix adds automatic cleanup of stale containers when encountering
   a name conflict:
   - Added DockerHttp409Error exception class
   - Updated http_query to detect 409 status codes
   - Modified create() to remove conflicting containers and retry

   Fixes the issue where opening a project fails with:
   "Docker has returned an error: 409 Conflict. The container name
   '/GNS3.xxx' is already in use by container 'xxx'"
2026-02-27 23:35:11 +08:00
..
2026-02-25 19:00:57 +08:00
2026-01-28 22:24:10 +08:00
2026-02-16 19:32:47 +08:00
2026-02-23 23:26:42 +08:00
2025-05-14 19:11:44 +02:00
2024-04-22 18:51:29 +07:00
2026-01-28 22:30:36 +08:00
2022-01-19 22:28:36 +10:30
2026-02-24 21:32:36 +08:00