Bug #10410

arvados source not clean with fresh arvbox in dev mode

Added by Joshua Randall almost 5 years ago. Updated almost 5 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
11/11/2016
Due date:
% Done:

0%

Estimated time:
(Total: 0.00 h)
Story points:
0.5

Description

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?


Subtasks

Task #10522: Review 10410-arvbox-rubyResolvedLucas Di Pentima

Associated revisions

Revision d2f9e780
Added by Peter Amstutz almost 5 years ago

Merge branch '10410-arvbox-ruby' refs #10410

Revision 5debe2b7 (diff)
Added by Peter Amstutz almost 5 years ago

Arvbox sets PATH, GEM_HOME and GEM_PATH in common.sh. refs #10410

History

#1 Updated by Peter Amstutz almost 5 years ago

I think what's going on is that arvbox is using Ruby 2.1 and an older version of bundler from Debian, so then the fix is to switch to using rvm and installing the latest bundler.

#2 Updated by Peter Amstutz almost 5 years ago

  • Target version set to 2016-11-23 sprint
  • Story points set to 0.5

10410-arvbox-ruby @ 4225d058e0bc4380203fe5959e7e54febc91e83b

Dockerfile now builds Ruby from source, so we can update Ruby independently from Debian packaging.

#3 Updated by Peter Amstutz almost 5 years ago

And installs latest bundler (instead of bundler from Debian) which eliminates the "Gemfile.lock" fighting.

#4 Updated by Peter Amstutz almost 5 years ago

  • Assigned To set to Peter Amstutz

#5 Updated by Tom Morris almost 5 years ago

  • Status changed from New to In Progress

#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 apt-get RUN lines 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-common package, 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 clean before apt-get update on every package install RUN line, but couldn’t understand why. (ex: http://stackoverflow.com/questions/35923576/debian-httpredir-mirror-system-unreliable-unusable-in-docker)

#7 Updated by Lucas Di Pentima almost 5 years ago

Reviewed updates at 5d2ef6f7a2a8f93ec411c420287f30af92294520
Successfully built arvbox locally at first attempt, so this LGTM, please merge.

#8 Updated by Peter Amstutz almost 5 years ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF