Docker build process is not working

ogecko / alpaca-benro-polaris

Open up the Benro Polaris Tripod Head with an HTTP-based REST API allowing applications to leverage the platform.

https://www.kickstarter.com/projects/jdmorriso/alpaca-benro-polaris-driver?ref=9a035f

MIT License

13 stars 0 forks source link

Docker build process is not working #23

Open joriws opened 5 hours ago

joriws commented 5 hours ago

Describe the bug Multiple Docker issues in docker/Dockerfile

./requirements.txt is not found => ./docker/requirements.txt fixes
./docker/entrypointALPACA.sh is not found => cp docker/entrypoint.sh docker/entrypointALPACA.sh
after image build entrypoint.sh is not executable
after it is executable there is no driver-folder - did you forget to git clone or copy the driver-part to image,

To Reproduce Steps to reproduce the behavior:

bash ./docker/run.sh -b -t "Europe/Helsinki"

Expected behavior Well the polaris:latest docker image to be build and container launched.

Platform (please complete the following information):

OS: RaspberryPi, Docker-ce

Additional context Add any other context about the problem here.

joriws commented 5 hours ago

then on every run it builds a new docker image..

`(ssc-3.12.5) pi@raspberrypi3bp:~/alpaca-benro-polaris/platforms $ docker image ls REPOSITORY TAG IMAGE ID CREATED SIZE polaris latest 4cb3b4402245 10 minutes ago 617MB

ec6a26fffb20 17 minutes ago 617MB 1c5a63af5945 18 minutes ago 617MB 9e35f13412fb 19 minutes ago 617MB 43582311f9ec 20 minutes ago 617MB c0a8d9afbc1b 21 minutes ago 617MB f0f19cd50102 23 minutes ago 617MB 05ffdab3ade3 38 minutes ago 617MB `

jdmorriso commented 2 hours ago

@joriws, thanks for the feedback on the Docker/Raspberry Pi issues. As you've probably guessed, these have yet to be completed or tested. I need some new equipment and a gap in another project before I can work on them.

If you have time and interest in helping with the project, let me know, and I can add you as a member and give you write access to create a branch for a pull request into the next version. If you can wait, I will probably address them before the next version, 1.0.1, is released.