You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
正在部署[░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ] 80% 600.2 sError: 部署失败,错误信息:[100001]deploy_fail, 请求RequestId:5d28f7fd-b600-4ac0-9466-8e482a71d4ee
at SamManager.<anonymous> (/Users/hanqin/.nvm/versions/node/v12.16.2/lib/node_modules/@cloudbase/cli/node_modules/@cloudbase/framework-core/lib/sam/index.js:93:35)
at Generator.next (<anonymous>)
at fulfilled (/Users/hanqin/.nvm/versions/node/v12.16.2/lib/node_modules/@cloudbase/cli/node_modules/@cloudbase/framework-core/lib/sam/index.js:5:58)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
✖ 部署失败,错误信息:[100001]deploy_fail, 请求RequestId:5d28f7fd-b600-4ac0-9466-8e482a71d4ee
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Issue-Label Bot is automatically applying the label bug to this issue, with a confidence of 0.79. Please mark this comment with 👍 or 👎 to give our bot feedback!
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
在部署nginx服务器时,nginx.conf的注释方式写错了,正确的为#,但我误写成 // 啦,在部署过程中并没有提醒。后来不得不在本地安装了docker,尝试 docker run 时才发现了问题。
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: