5 Commits

Author	SHA1	Message	Date
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
grossmj	f928738bd5	Use pyupgrade with --py36-plus param.	2021-04-13 18:37:58 +09:30
Julien Duponchelle	d8bdd16e13	Raise an error if image is missing on compute	2016-06-07 15:34:04 +02:00
grossmj	5a76f81271	Refactoring to use a common node class for all VMs and other (future) objects.	2016-05-11 11:35:36 -06:00
Julien Duponchelle	58d4a529d4	Rename hypervisor to compute ... Fix #487	2016-04-15 17:59:59 +02:00