new cube clt and mx version

new docker registry

.devcontainer/devcontainer.json

@@ -4,19 +4,35 @@
 	"name": "Debian",
 	// Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
 	"dockerFile": "../CubeMx/Dockerfile",
-	"privileged": true,
-	"forwardPorts": [14500, 14500]
+	"mounts": [
+    // 1. Share the X11 socket for GUI display
+    "source=/tmp/.X11-unix,target=/tmp/.X11-unix,type=bind,consistency=cached",
 
-	// Features to add to the dev container. More info: https://containers.dev/features.
-	// "features": {},
+    // 2. Share the D-Bus system socket (resolves the system_bus_socket error)
+    "source=/var/run/dbus/system_bus_socket,target=/var/run/dbus/system_bus_socket,type=bind,consistency=cached",
 
-	// Use 'forwardPorts' to make a list of ports inside the container available locally.
-	// "forwardPorts": [],
+    // 3. Share .Xauthority for X11 authorization (resolves "Authorization required" error)
+    //    Ensure the target path matches the container user's home.
+    "source=/run/user/1000/xauth_MASbDk,target=/home/vscode/.Xauthority,type=bind,consistency=cached"
+    // Make sure to adjust /home/vscode if your container user's home directory is different.
+  ],
 
-	// Configure tool-specific properties.
-	// "customizations": {},
+  "containerEnv": {
+    // 4. Set the DISPLAY variable to use the host's X server
+    "DISPLAY": "${localEnv:DISPLAY}",
 
-	// Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
-	// "remoteUser": "root"
+    // 5. If using .Xauthority mount, point to its location in the container
+    "XAUTHORITY": "/home/vscode/.Xauthority"
+  },
+
+  // Optional: Command to ensure the container user owns the .Xauthority file if mounted.
+  // Adjust 'vscode' if your container user is different.
+  // "postCreateCommand": "sudo chown vscode:vscode /home/vscode/.Xauthority || echo 'Xauthority not found or permission change failed, this might be okay.'",
+
+
+  // Generally, avoid privileged: true.
+  // If you encounter permission issues that aren't solved by the above,
+  // adding specific capabilities is safer.
+  "privileged": true
 	
-}
+}