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
..
2024-12-17 15:08:45 +07:00
2026-02-21 21:42:22 +08:00
2026-02-23 17:10:15 +08:00
2022-01-19 22:28:36 +10:30
2022-01-19 22:28:36 +10:30
2021-04-13 18:46:50 +09:30
2021-04-13 18:46:50 +09:30
2023-01-05 12:38:00 +08:00