microsoft / microsoft/vscode-containers
Add "unpause" option to paused containers
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 139
- Forks
- 87
- Avg merge
- 9h 15m
- Merged PRs (30d)
- 9
Description
Repro steps:
- Pause a container
- Right click on the container, select start
Expected:
Start works or I can "unpause"
Actual:
Start doesn't work and there is no unpause
Action: vscode-docker.containers.start
Error type: 409
Error Message: (HTTP code 409) unexpected - cannot start a paused container, try unpause instead
Version: 0.7.1-alpha
OS: darwin
Product: Visual Studio Code
Product Version: 1.36.1
Language: en
Call Stack
docker-modem/modem.js:257:17
getCause docker-modem/modem.js:287:7
Modem.buildPayload docker-modem/modem.js:256:5
IncomingMessage.<anonymous> docker-modem/modem.js:232:14
IncomingMessage.emit events.js:187:15
endReadableNT _stream_readable.js:1092:12
process._tickCallback next_tick.js:63:19
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the vscode-docker.containers.start action and reproduce the reported 409 response with a paused container. Trace how container actions are exposed in the extension, then add an unpause path or option so the paused container can be resumed; done means the reported start interaction no longer fails for paused containers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100