arvados source not clean with fresh arvbox in dev mode
after running `arvbox reboot dev` for the first time:
# cd /usr/src/arvados # git status On branch master Your branch is up-to-date with 'origin/master'. Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: apps/workbench/Gemfile.lock Untracked files: (use "git add <file>..." to include in what will be committed) sdk/cli/binstubs/ sdk/cwl/arvados_cwl/_version.py services/api/config/arvados-clients.yml
I guess there is a known recurring issue with Gemfile.lock, but it seems like the latter three untracked files should probably be included in .gitignore?
#6 Updated by Lucas Di Pentima almost 5 years ago
Having some issues installing the new arvbox locally, but in the meantime I have some comments:
- Instead of splitting installs into more layers, I found an option that maybe will help when download errors happen:
apt-get -o Acquire::Retries=N
- I think it may be necessary to prepend all
RUNlines with an
apt-get update &&command, as I’m trying to create the new arvbox image, in my case the process tried to download an old version (non-existant on the remote server) of the
mysql-commonpackage, failing every time with 404.
- I also found several pages (including stackoverflow posts) that claim to solve or greatly diminish the “intermittent debian mirror network problem” by prepending
apt-get updateon every package install
RUNline, but couldn’t understand why. (ex: http://stackoverflow.com/questions/35923576/debian-httpredir-mirror-system-unreliable-unusable-in-docker)