Error compiling Ripple/Vagrant/Docker stack

Archived Categories Ripple OSI
1

Hello all,
Following the instructions at “GitHub - RippleOSI/Ripple-Stack-Vagrant-Docker: for docker & vagrant files to help with RippleOSI stack setup -check Qewd-Courier+HIT work for latest Docker setup”
After vagrant up command was issued, the compiling grounded to a halt after these statements.

…
default: Running docker-compose build…
==> default: conductor-service-phr uses an image, skipping
==> default: openid-connect-server uses an image, skipping
==> default: mpi-service uses an image, skipping
==> default: authentication-service-phr uses an image, skipping
==> default: cdr-service-openehr uses an image, skipping
default: Running docker-compose up…
==> default: readlink /var/lib/docker/overlay2: invalid argument
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

Can someone kindly suggested what might have caused the error “readlink /var/lib/docker/overlay2: invalid argument” ?
Thanks in advance.
Sorcerer

2

OK, I isolated the problem. The problem is:
default: Guest Additions Version: 5.1.38
default: VirtualBox Version: 6.0
So, I have to use brute force “Docker provisioner” to start everything.
Sorcerer

1 Like
3

Hi @sorcerer glad you found the error. Are those defaults hard-coded in the Vagrantfile somewhere? It’s a long time since I wrote those scripts so I can’t remember much about it.

(To be honest, Docker support on Windows is much better now, so actually there’s an argument you don’t need the Vagrant wrapper any more and could just use Docker Machine (or whatever it is on Windows) with the Docker Compose file.)

Is this solved by using Docker provisioner?

4

Hello Marcus,
Thanks for responding.
Yes, indeed. Docker provisioner fixed the version issue.
The versioning # is not hardcoded in vagrantfile. So, somewhere, the version # must be hard coded.
Regards,
Sorcerer