Closed Fryguy closed 2 years ago
Ugh I give up for today - bundler is a pain in my neck.
Ugh I give up for today - bundler is a pain in my neck.
Warning: the running version of Bundler (2.1.4) is older than the version that created the lockfile (2.2.24). We suggest you to upgrade to the version that created the lockfile by running `gem install bundler:2.2.24`.
The dependency httpd_configmap_generator (>= 0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for x86_64-darwin-19 but the dependency is only for ruby, ruby, ruby, ruby, ruby, ruby, ruby, ruby, ruby, ruby, ruby, ruby, ruby, ruby, ruby, ruby, ruby, ruby, ruby, ruby, ruby, ruby, . To add those platforms to the bundle, run `bundle lock --add-platform ruby ruby ruby ruby ruby ruby ruby ruby ruby ruby ruby ruby ruby ruby ruby ruby ruby ruby ruby ruby ruby ruby `.
Unable to find a spec satisfying httpd_configmap_generator (>= 0) in the set.
Perhaps the lockfile is corrupted?
ruby ruby ruby ruby ruby ruby... WAT 🤣
I'm tempted to not install the gem at all, and just COPY
with bundle update
and be done with it
In order to make bundler respect the Gemfile when we run the CLI, we need to have both development and regular dependencies pre-resolved. This is the point of the Gemfile.lock, so we need to commit it. In the Dockerfile we only install the gem, which only installs non-dev dependencies, but bundler still needs the full resolution tree which is in the Gemfile.lock.
Fixes #55
@jrafanie Please review.