docker-compose.yml doesn't actually start inbox-api
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 30
- Forks
- 13
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 8
Description
Running docker compose up doesn't bring the app container up. In fact, neither the Dockerfile or docker-compose.yml have a command to run.
Adding a command (bin/inbox-api.py) results in an import problem for the inbox module (because inbox isn't actually installed to the container's python):
Attaching to app-1
app-1 | Could not find 'inbox' Python package installation. Maybe the Vagrant box provisioning didn't succeed?
app-1 | Try running sudo ./setup.sh
app-1 exited with code 1
Contributor guide
No contributing guide indexed for this repository
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 with docker-compose.yml and Dockerfile, then inspect bin/inbox-api.py and the reported inbox import failure. Run docker compose up and verify that the app container starts with the inbox-api command and finds the installed inbox package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, python
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100