Visual studio code 即使在devcontainer.json上引用了映像，也无法运行容器映像

我在Ubuntu 18.04的VS代码（1.35.0版）上使用远程容器扩展（0.59.0版），当我点击远程容器：重新打开容器中的文件夹时，我得到了以下错误（我删除了mycustomimage id）：

Setting up container for folder: /home/user/source/project
Run: docker exec mycustomimage-id test -d /root/.vscode-server
cannot exec in a stopped state: unknown
Run: docker exec mycustomimage-id test -d /root/.vscode-remote
Error response from daemon: Container mycustomimage-id is not running
Run: docker exec mycustomimage-id /bin/sh -c set -o noclobber ; mkdir -p '/root/.vscode-server/data/Machine' && { > '/root/.vscode-server/data/Machine/.writeMachineSettingsMarker' ; } 2> /dev/null
Error response from daemon: Container mycustomimage-id is not running
Run: docker exec mycustomimage-id /bin/sh -c (cat /etc/os-release || cat /usr/lib/os-release) 2>/dev/null
Error response from daemon: Container mycustomimage-id is not running
Run: docker exec mycustomimage-id test -d /root/.vscode-server/bin/553cfb2c2205db5f15f3ee8395bbd5cf066d357d
Error response from daemon: Container mycustomimage-id is not running
Installing VS Code Server for commit 553cfb2c2205db5f15f3ee8395bbd5cf066d357d
Run: docker exec mycustomimage-id mkdir -p /root/.vscode-server/bin/553cfb2c2205db5f15f3ee8395bbd5cf066d357d_1560180323972
Error response from daemon: Container mycustomimage-id is not running

我的

devcontainer.json

如下所示：

// See https://aka.ms/vscode-remote/devcontainer.json for format details.
{
    "name": "Load image",
    "context": "..",
    "image": "mycustomimage:20190531",
    "runArgs": [    
        "--cap-add=SYS_PTRACE",
        "--security-opt",
        "seccomp=unconfined",
        "-e", "REPO_TOKEN=${env.REPO_TOKEN}",
        "-e", "BUILD_CONFIGURATION=Debug",
        "--entrypoint","/bin/bash"
    ],

    "extensions": ["ms-vscode.cpptools"],
    "workspaceFolder": "/src/remoteproj",
    "workspaceMount": "source=/home/user/source/project,destination=/src/remoteproj,type=bind"  
}

---

我试过运行容器，也试过当我没有任何运行容器时。我如何确保devcontainer.json中引用的图像与VS代码试图启动的图像相同？

我也遇到了这个问题，我完全不知道这可能是什么。对于任何可能偶然发现这个问题的人，我在重新启动并运行docker rm$（docker ps-qa）后都没有看到错误，不知道是谁修的。