ravada icon indicating copy to clipboard operation
ravada copied to clipboard

Still having problems with docker install

Open cberz opened this issue 4 years ago • 4 comments

While trying to finish the installation it still gives errors despite the changes made on last commit. I followed the last documentation step by step and this is the results

:~/src/ravada/dockerfy$ sudo docker-compose up -d Creating network "ravada_network" with the default driver Creating ravada-mysql ... done Creating ravada-front ... done Creating ravada-back ... done :~/src/ravada/dockerfy$ sudo docker exec -it ravada-back bash root@a4164b79b4a7:/ravada# PERL5LIB=./lib ./script/rvd_back --add-user soporte bash: ./script/rvd_back: No such file or directory

cberz avatar Apr 08 '20 19:04 cberz

To help you out, please tell us what environment you are testing it in. Operating system, version of Docker, Docker-compose and everything that can give us a better idea of what is happening to it. Remember that the project code must be in your home ~/src/ravada

fv3rdugo avatar Apr 08 '20 20:04 fv3rdugo

Operating System: Debian GNU/Linux 10 (buster) Kernel: Linux 4.19.0-8-amd64 Architecture: x86-64 Docker version 19.03.8, build afacb8b7f0 docker-compose version 1.25.4, build 8d51620a

Yeah, im on the expected folder, I followed all steps from documentation and read about docker issues opened and closed here but still got it. i also tried

~/src/ravada/dockerfy$ sudo docker exec -it ravada-back bash
root@a4164b79b4a7:/ravada# PERL5LIB=./lib ./script/rvd_back --add-user soporte
bash: ./script/rvd_back: No such file or directory
root@a4164b79b4a7:/ravada# bin/rvd_back.pl --add-user soporte
bash: bin/rvd_back.pl: No such file or directory

cberz avatar Apr 08 '20 20:04 cberz

We solved an issue #1299. Maybe that affected you.

fv3rdugo avatar Apr 20 '20 11:04 fv3rdugo

The issue is that in the docker-compose.yml, the mount for the /ravada directory inside the containers is linked to:

~/src/ravada/

That means that for users that git clone the repo from their user account and then run docker with sudo (or a different user), the directory does not get mounted inside the container because ~/src/ravada/ points to /root/src/ravada instead of "username"/src/ravada.

sotiris-bos avatar May 09 '20 18:05 sotiris-bos