build failed

[zjline]

When I run “docker-compose up -d --build --remove-orphans”，there was an error：

_Step 14 : RUN bundle install
 ---> Running in 0767e932eea3
########
there are maney code I didn't copy
#######

Gem::InstallError: rdoc requires Ruby version >= 2.2.2.
An error occurred while installing rdoc (6.0.1), and Bundler cannot continue.
Make sure that `gem install rdoc -v '6.0.1'` succeeds before bundling

In Gemfile:
  sdoc was resolved to 1.0.0, which depends on
    rdoc
ERROR: Service 'fluxday-app' failed to build: The command '/bin/sh -c bundle install' returned a non-zero code: 5_

So who can help me ?thanks

[yumenoshizuku]

Add
gem 'rdoc', '5.1.0'
in Gemfile
before

group :doc do
  # bundle exec rake doc:rails generates the API under doc/api.
  gem 'sdoc', require: false
end

[kurtferreira]

Alternatively, update the Dockerfile to use Ruby 2.2 instead of 2.1:

RUN apt-get install -y nodejs \ ruby2.2 \ ruby2.2-dev \ build-essential \ curl \ zlib1g-dev \ libssl-dev \ libreadline-dev \ libyaml-dev \ libxml2-dev \ libxslt-dev \ libpq-dev \ git python-virtualenv \ libmysqlclient-dev \ libmagickwand-dev \ gnuplot \ imagemagick-doc \ imagemagick \ wkhtmltopdf

[louisyssel]

Kurt, can you suggest which Ruby 2.2 should be used? 2.2.1, 2.2.2 or which one?

[kurtferreira]

@louisyssel Simply changing it to 2.2 seemed to do the trick but I had a cascade of other issues such as the DB and seeding etc. and as a result and eventually gave up. Pity, because Fluxday is a nifty tool but to get the environment set up and installed from Docker (which should be a really easy feat) was just too cumbersome and I lack the time to issue a PR for my changes. If do you manage to get the build process sorted, please do drop me a message, I'd greatly appreciate it.

[louisyssel]

In all fairness Kurt, as per your message, I also gave up. Irt is an awesome tool, and I would love to use it, but it is simply too cumbersome to get it running. I did not want to use Docker, I wanted to install on a dedicated server, as I wanted to use it for projects with larger teams, but the issue also seems to be that they do not support the latest versions of mysql, as they are using db calls that is no longer allowed. Also, Rails 2.2 is now barely supported, but the latest version is already 2.5.x. I cannot see that this will last for long, as getting it to run is just too much hassle. If they do this properly at some stage and update it it properly, I will look gain. Thanks for the help Louis [/Users/louisy/Library/Containers/com.microsoft.Outlook/Data/Library/Caches/Signatures/signature_2118410492] Louis Yssel Chief Technology Officer M: +27 82 908 9222 T: +27 87 135 1114 A: 5 Delmore Street, Midstream Estate V: louis@connectionhub.call.sl W: http://www.uc247.co.za From: Kurt Ferreira <notifications@github.com> Reply-To: foradian/fluxday <reply@reply.github.com> Date: Friday, 27 July 2018 at 12:56 To: foradian/fluxday <fluxday@noreply.github.com> Cc: Louis Yssel <louis@uc247.co.za>, Mention <mention@noreply.github.com> Subject: Re: [foradian/fluxday] build failed (#45) @louisyssel<https://github.com/louisyssel> Simply changing it to 2.2 seemed to do the trick but I had a cascade of other issues such as the DB and seeding etc. and as a result and eventually gave up. Pity, because Fluxday is a nifty tool but to get the environment set up and installed from Docker (which should be a really easy feat) was just too cumbersome and I lack the time to issue a PR for my changes. If do you manage to get the build process sorted, please do drop me a message, I'd greatly appreciate it. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#45 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AcMl28RSStj8bw8XomFNY10siPWeiJBMks5uKvHwgaJpZM4SZlVp>.

[haison123]

Help me pls!!!!
after run docker-compose up -d --build --remove-orphans , there was an error:

E: Sub-process /usr/bin/dpkg returned an error code (1)
ERROR: Service 'fluxday-app' failed to build: The command '/bin/sh -c apt-get upgrade -y' returned a non-zero code: 100