st2ctl in Docker environment
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
st2ctl assumes it's running in a VM environment and wasn't designed to be executed inside the Docker. We'll need to improve that.
Because listing processes or starting services is not viable in a Docker environment, where each service runs in its own Docker container, st2ctl needs a simple modification so it doesn't try to query list of processes but instead suggest to use Docker cmd.
Example commands which don't work in Docker environment:
st2ctl statusst2ctl stopst2ctl startst2ctl restartst2ctl restart-componentst2ctl reopen-log-filesst2ctl reloadlists running processes as well
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 by locating the st2ctl implementation and the handlers for status, stop, start, restart, restart-component, reopen-log-files, and reload. Check how these commands query processes or manage services, then verify that Docker users are directed to Docker commands instead; the listed commands should no longer attempt VM-style process or service management in Docker.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100