Persistent "build.docker.path not specified" error despite correct launch.json

[schizos1]

Describe your setup:
Host OS: macOS (your MacBook)
Remote OS: Ubuntu 24.04
VS Code Version: 버전: 1.101.0 (Universal)
커밋: dfaf44141ea9deb3b4096f7cd6d24e00c147a4b1
날짜: 2025-06-11T15:00:50.123Z
Electron: 35.5.1
ElectronBuildId: 11727614
Chromium: 134.0.6998.205
Node.js: 22.15.1
V8: 13.4.114.21-electron.0
OS: Darwin arm64 24.5.0
Cloud Code Extension Version: 2.31.1
Minikube Version: v1.36.0
Docker Version: Server: Docker Engine - Community
Engine:
Version: 28.2.2
API version: 1.50 (minimum version 1.24)
Go version: go1.24.3
Git commit: 45873be
Built: Fri May 30 12:07:27 2025
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.7.27
GitCommit: 05044ec0a9a75232cad458027ca83437aae3f4da
runc:
Version: 1.2.5
GitCommit: v1.2.5-0-g59923ef
docker-init:
Version: 0.19.0
GitCommit: de40ad0
Problem Description:
You are trying to run a Node.js application locally using Cloud Code's "Cloud Run: Run/Debug Locally" feature.
You have created a Dockerfile for your Node.js app.
The error build.docker.path not specified... consistently appears, even though launch.json explicitly defines dockerfile and context under build.docker.
Steps Taken (What you've tried):
Initial setup with Docker and Minikube on Ubuntu server (including adding user to docker group, rebooting).
Confirmed Docker hello-world runs successfully.
Tried Buildpacks (failed with permission denied on /layers/group.toml).
Switched to Dockerfile build method.
Corrected launch.json (explicitly showing the content that caused the error previously, and the final version you just shared).
Performed docker system prune -a --volumes --force.
Performed minikube stop && minikube delete --profile cloud-run-dev-internal && minikube start --profile cloud-run-dev-internal --driver=docker --container-runtime=docker.
Removed ~/.vscode-server/ on Ubuntu.
Uninstalled and reinstalled Cloud Code extension on the remote.
Full VS Code restarts and SSH reconnections after every major change.
Mention that ports, makeServiceAccessible, autoRebuild properties caused "not allowed" warnings, and they were removed, but the main error persists.