Closed jhpoelen closed 6 years ago
You shouldn't need sudo, but that's likely not the problem.
Good point about sudo, I should probably change the way I configure docker. Regarding the actual issue - am trying to see whether upgrading to 18.04 fixes it.
I've replicated the problem on Mac.
Did you every consider running all this in travis every week or so?
That should catch variability introduced by apt update
We have definitely wanted to get the CI/CD pipeline rolling, just been a matter of getting it setup.
I can do that now, it think it'll save time in fixing this issue. Perhaps easier if you add me as a contributor. Alternatively, I can do the pull request method and you'll have to manually enable travis / merge pull requests. Let me know what you prefer.
Added you here. Pushed fix.
We just did a major branch merge hours ago. Expect other bumpiness. I see Ruby in dockerfile needs to be bumped as well.
Ok, fastening my seatbelt ; )
Still an issue with getting right Ruby version. Back at it ASAP but off for a bit.
docker-compose build
working on mac/ubuntu 16.04
looks like travis has similar results. Closing issue.
when running
sudo docker-compose build
on ubuntu 18.04 with docker v17.12.1-ce, the following error message is found: