Unable to install pack from local directory
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6.5k
- Forks
- 787
- PR merge metrics
- No merged PRs in 30d
Description
SUMMARY
Upon trying to install a known working pack from a local directory within the StackStorm Docker client container, the installation fails with ValueError: Local pack directory "/opt/stackstorm/test_pack" doesn't exist.
STACKSTORM VERSION
st2 3.6.0, on Python 3.6.9
OS, environment, install method
Docker container, using the official Docker Compose config. Host environment is Arch Linux running 5.17.5. All commands are executed from within the st2client container.
Steps to reproduce the problem
- Obtain copy of working pack on local computer. The linked pack installs fine when installing directly from GitHub.
- Copy local pack to
st2clientcontainer:docker compose cp ~/repos/test_pack st2client:/opt/stackstorm/(on host machine, fromst2-dockerdirectory) - Attempt to install pack:
st2 pack install file:///opt/stackstorm/test_pack(from withinst2clientcontainer)
Expected Results
The pack installs successfully, as it does when installing from GitHub.
Actual Results
Install fails with ValueError: Local pack directory "/opt/stackstorm/test_pack" doesn't exist. As a sanity check, the directory does exist:
root@667335d8ca8c:/opt/stackstorm# ls /opt/stackstorm
configs exports packs packs.dev rbac st2 test_pack virtualenvs
Thank you for any assistance!
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
Reproduce the failure inside the st2client container using the documented docker compose copy and st2 pack install file:///opt/stackstorm/test_pack commands. Start by tracing how the CLI validates local pack paths; done means the known working local pack installs successfully, matching installation from GitHub.
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
- 42/100