Docker image https://hub.docker.com/r/errbotio/errbot not including --init step
Need help with
- [X] Running the bot
- [ ] Writing plugin
- [ ] Other
Issue description Please describe the issue. The more information you can provide, the better.
When running the docker image, errbot is not initialised.
If I clone the repository and build the dockerfile into an image and run it, errbot is initialised. I suspect something might be happening with publish or the registry itself.
Steps to reproduce Provide steps to reproduce the behavior or include sample plugin code.
❯ docker run errbotio/errbot:latest
I cannot find the config file /home/errbot/config.py.
You can change this path with the -c parameter see --help
## log in to container was unable to view the config dir and files under /home/errbot
❯ docker run -it --entrypoint bash errbotio/errbot:latest
Unable to find image 'errbotio/errbot:latest' locally
latest: Pulling from errbotio/errbot
bd159e379b3b: Already exists
de08aeb7fd50: Already exists
6dd159998355: Already exists
4d872ce7a60f: Already exists
962145d175ca: Already exists
7b84f1a039e8: Pull complete
86b38485caa5: Pull complete
85caf9e28395: Pull complete
Digest: sha256:b1d52601d27013f219f6a153ae949ac91e2f4c5b22d0a5a56734c0fd65318f27
Status: Downloaded newer image for errbotio/errbot:latest
errbot@665841e0dbe0:~$ pwd
/home/errbot
errbot@665841e0dbe0:~$ ls -lrt
total 0
Environment (please complete the following information):
- Errbot version: latest
- OS version: macOS Monterey 12.6
- Python version: n/a
- Using a virtual environment: no
- Using Docker: yes
Additional info If you have any more information, please specify it here.
This is strange. The Dockerfile does include an init step, so a file should be present in build.
I'm pretty sure it's because the Dockerfile runs
errbot --init instead of /usr/local/bin/errbot --init or whatever is the same in the entry point
Just a follow up, I edited dockerfile locally and was able to get it working when I ran with the whole path instead for errbot cmd.
I'll double check however I'm quite sure it's present.
The /usr/local/bin, I believe, is part of PATH, so it should be necessary to run use the full bin path.