Enabling server with unsupported architecture blocks MCP Gateway startup

[xenoscopic]

Enabling an MCP server with an unsupported architecture (e.g. the Gmail MCP Server) will cause the gateway to fail to start. For example, enabling the Gmail MCP Server on an Apple Silicon Mac (i.e. linux/arm64/v8) will succeed, but then invoking docker mcp gateway run will show:

- Using images:
  - ...
  - yashtekwani/gmail-mcp@sha256:9d806c6ba3752bd83a94782cc65d79929e05b3d4d805a01320d86004e39daf13
pulling docker images: pulling docker image yashtekwani/gmail-mcp@sha256:9d806c6ba3752bd83a94782cc65d79929e05b3d4d805a01320d86004e39daf13: Error response from daemon: no matching manifest for linux/arm64/v8 in the manifest list entries: no match for platform in manifest: not found

and terminate. No other MCP servers can be used until the unsupported server is removed and their is no graphical reporting of the pull failure.

[slimslenderslacks]

Verified fix with the current gmail-mcp.