{"categories":[],"published":"2023-08-31 13:06:10","blog_title":"\u30b5\u30fc\u30d0\u30fc\u30ef\u30fc\u30af\u30b9\u30a8\u30f3\u30b8\u30cb\u30a2\u30d6\u30ed\u30b0","image_url":null,"title":"\"Error: spawnSync docker ENOENT\"\u306e\u89e3\u6d88\u65b9\u6cd5","author_name":"swx-yuji-kumagai","blog_url":"https://blog.serverworks.co.jp/","provider_name":"Hatena Blog","version":"1.0","type":"rich","description":"\u3053\u3093\u306b\u3061\u306f\u3001SWX3\u4eba\u76ee\u306e\u718a\u8c37\uff08\u60a0\uff09\u3067\u3059\u3002 \u4eca\u56de\u306fCDK\u3067\u51fa\u305f\u30a8\u30e9\u30fc\u3092\u76f4\u3057\u305f\u5099\u5fd8\u9332\u3067\u3059\u3002 \u30a8\u30e9\u30fc $ cdk bootstrap Error: spawnSync docker ENOENT at Object.spawnSync (node:internal/child_process:1110:20) at Object.spawnSync (node:child_process:871:24) at dockerExec (/example-app/node_modules/aws-cdk-lib/core/lib/bundling.ts:498:16) at Function.from\u2026","author_url":"https://blog.hatena.ne.jp/swx-yuji-kumagai/","provider_url":"https://hatena.blog","height":"190","html":"<iframe src=\"https://hatenablog-parts.com/embed?url=https%3A%2F%2Fblog.serverworks.co.jp%2F2023%2F08%2F31%2F130610\" title=\"&quot;Error: spawnSync docker ENOENT&quot;\u306e\u89e3\u6d88\u65b9\u6cd5 - \u30b5\u30fc\u30d0\u30fc\u30ef\u30fc\u30af\u30b9\u30a8\u30f3\u30b8\u30cb\u30a2\u30d6\u30ed\u30b0\" class=\"embed-card embed-blogcard\" scrolling=\"no\" frameborder=\"0\" style=\"display: block; width: 100%; height: 190px; max-width: 500px; margin: 10px 0px;\"></iframe>","width":"100%","url":"https://blog.serverworks.co.jp/2023/08/31/130610"}