sameersbn / sameersbn/docker-gitlab

Docker build fails when installing dependency omniauth-google-oauth2

Open
#1,512 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

wontfix
Dominant language
Shell
Stars
8.1k
Forks
2.1k
Avg merge
17h 47m
Merged PRs (30d)
7

Description

Hi,
I am not able to build the docker container, i am facing this error:

Downloading omniauth-google-oauth2-0.4.1 revealed dependencies not in the API or
the lockfile (omniauth-oauth2 (>= 1.3.1), jwt (~> 1.5.2)).
Either installing with `--full-index` or running `bundle update
omniauth-google-oauth2` should fix the problem.

In Gemfile:
  omniauth-google-oauth2
The command '/bin/sh -c bash -x ${GITLAB_BUILD_DIR}/install.sh' returned a non-zero code: 34

in this step:

Step 7/15 : RUN bash -x ${GITLAB_BUILD_DIR}/install.sh ---> Running in 8ee404ceb3b5
This happens when running this line
+ sudo -HEu git bundle install -j4 --deployment --without development test aws

After investigations, it seems that it has something todo with ruby dependencies and there is some version conflicts :
https://gitlab.com/gitlab-org/gitlab-ce/commit/b60a14357f443445771ce486bc498188545cd62e

I am not very comfy with Gem and ruby, can you help please.

This is my version info:

ENV GITLAB_VERSION=9.0.4 \
    RUBY_VERSION=2.3 \
    GOLANG_VERSION=1.6.3 \
    GITLAB_SHELL_VERSION=5.0.0 \
    GITLAB_WORKHORSE_VERSION=1.4.2 \
    GITLAB_PAGES_VERSION=0.4.0 \
    GITLAB_USER="git" \
    GITLAB_HOME="/home/git" \
    GITLAB_LOG_DIR="/var/log/gitlab" \
    GITLAB_CACHE_DIR="/etc/docker-gitlab" \
    RAILS_ENV=production
root@debian:~/docker/src/docker-gitlab# git show
commit 7cc6e3a3eccb81cf4f3283bacf21a0768456a6df
Author: solidnerd <niclas@mietz.io>
Date:   Sun Apr 9 22:34:59 2017 +0200

    release 9.0.4

For now, we are not ready to upgrade to a new gitlab version

Regards

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Docker build step that runs bash -x ${GITLAB_BUILD_DIR}/install.sh, then inspect the Gemfile and the bundle install --deployment command. Reproduce the failure using GitLab 9.0.4 and the listed Ruby version, and compare the dependency conflict with the linked upstream commit. Done means the Docker build completes successfully without requiring a newer GitLab version.

Written by the indexing model from the issue text.

Assessment

Tech stack
bash, docker, ruby
Domain
build-system, devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.