Fix container inspection failure for containers with unmapped ports (#293)

Author: Copilot

package-lock.json

@@ -1,3 +1,7 @@
+## 0.4.2 - 8 September 2025
+### Fixed
+* Fixed an issue where inspection could fail if a container had unmapped ports. [#292](https://github.com/microsoft/vscode-docker-extensibility/issues/292)
+
 ## 0.4.1 - 22 July 2025
 ### Fixed
 * Now depends on `@microsoft/vscode-container-client` v0.1.1, in order to get a fix. [#280](https://github.com/microsoft/vscode-docker-extensibility/issues/280)

packages/vscode-container-client/CHANGELOG.md

@@ -1,7 +1,7 @@
 {
     "name": "@microsoft/vscode-container-client",
     "author": "Microsoft Corporation",
-    "version": "0.4.1",
+    "version": "0.4.2",
     "description": "Extensibility model for implementing container runtime providers (shared by VS and VS Code)",
     "license": "See LICENSE in the project root for license information.",
     "repository": {

packages/vscode-container-client/package.json

@@ -61,7 +61,7 @@ const DockerInspectContainerHostConfigSchema = z.object({
 const DockerInspectContainerNetworkSettingsSchema = z.object({
     Networks: z.record(z.string(), DockerInspectContainerNetworkSchema).nullable().optional(),
     IPAddress: z.string().optional(),
-    Ports: z.record(z.string(), z.array(DockerInspectContainerPortHostSchema)).nullable().optional(),
+    Ports: z.record(z.string(), z.array(DockerInspectContainerPortHostSchema).nullable().optional()).nullable().optional(),
 });
 
 const DockerInspectContainerStateSchema = z.object({