YueGuobin d8f8b6ec70
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-07-13 09:57:55 +02:00
..
2026-05-08 19:03:14 +08:00
2026-05-18 21:49:01 +03:00
2026-04-09 20:25:44 +08:00
2026-04-10 20:27:46 +08:00
2024-04-22 18:51:29 +07:00
2026-04-08 20:02:01 +08:00
2015-01-13 17:05:26 -07:00
2026-05-08 19:06:04 +08:00
2024-01-28 12:13:07 +11:00
2026-01-24 18:51:44 +08:00
2026-05-08 20:03:31 +08:00