<hgm>
are there any community guidelines I can follow?
<hgm>
got em, rules! no need to bother anyone
drincruz has joined #ruby
ur5us has quit [Ping timeout: 245 seconds]
hgm has quit [Quit: Client closed]
drincruz has quit [Ping timeout: 255 seconds]
<adam12>
jimeh: I was going to use Github Packages but I agree with the tedius auth, at least in this specific scenario I have. I remember fighting with Geminabox last time I looked into this, so I didn't bother this time. I ended up writing my own solution in ~ 100 lines so I think I'm going with that O_O. Thanks for replying!
lunarkitty has quit [Quit: Connection closed for inactivity]
ur5us has quit [Remote host closed the connection]
ur5us has joined #ruby
ua_ has quit [Ping timeout: 255 seconds]
ua_ has joined #ruby
ur5us has quit [Ping timeout: 255 seconds]
_ht has joined #ruby
jetchisel has joined #ruby
menace has quit [Quit: menace]
jetchisel has quit [Max SendQ exceeded]
pwnd_sfw has quit [Read error: Connection reset by peer]
pwnd_sfw has joined #ruby
jetchisel has joined #ruby
jetchisel has quit [Ping timeout: 255 seconds]
jetchisel has joined #ruby
Bounga has joined #ruby
teclator has joined #ruby
TomyWork has joined #ruby
Tempesta has quit [Quit: See ya!]
Tempesta has joined #ruby
lunarkitty has joined #ruby
ur5us has joined #ruby
chris- has joined #ruby
ur5us has quit [Ping timeout: 255 seconds]
Rounin has joined #ruby
drincruz has joined #ruby
goldfish has joined #ruby
bandithijo has quit [Ping timeout: 258 seconds]
lunarkitty has quit [Quit: Connection closed for inactivity]
gearnode has quit [Ping timeout: 255 seconds]
darkxploit has joined #ruby
bandithijo has joined #ruby
bandithijo has quit [Quit: WeeChat 3.2-rc1]
Rounin has quit [Ping timeout: 252 seconds]
gearnode has joined #ruby
jetchisel has quit [Ping timeout: 245 seconds]
jetchisel has joined #ruby
jetchisel has quit [Quit: Unfortunately time is always against us -- [Morpheus]]
Garb0 has joined #ruby
aeris has quit [Remote host closed the connection]
goldfish has quit [Ping timeout: 268 seconds]
aeris has joined #ruby
Garb0 has quit [Quit: Garb0]
ikke has quit [Ping timeout: 255 seconds]
elf_fortrez has joined #ruby
ikke has joined #ruby
gr33n7007h has joined #ruby
Bounga has quit [Ping timeout: 252 seconds]
pwnd_sfw has quit [Quit: Ping timeout (120 seconds)]
jwr has joined #ruby
pwnd_sfw has joined #ruby
<jwr>
I'm installing rbenv and doing `bundle install` in one container, and that works as expected. I'm then copying the rbenv installation and the gems into another container, with the exact same Gemfile[.lock], and in that container bundler is saying my lockfile is corrupted. Can anybody tell me what I'm missing? https://pastebin.com/DXiskW60
<adam12>
jwr: can you install rails manually in that same container? `gem install rails -v 6.0.3.1`
<jwr>
adam12: yes
<adam12>
jwr: do you know the path where bundler installs it's gems in the first step? is it under ~/.rbenv or /app?
<adam12>
jwr: what happens if you just run `bundle`?
ikke has joined #ruby
<jwr>
adam12: gems are installed in the first place in /app/vendor/bundle. if i just run `bundle` it prints a bunch of `Using somegem...` lines, with the expected gems and versions (eg. rails 6.0.3.1 is there).
<adam12>
jwr: interesting...
<jwr>
adam12: weirdly it only seems to be an issue with `bundle update`. `bundle install` works fine (in the second/final container, where all the gems are already installed).
<weaksauce>
cat gemfile.lock
<weaksauce>
is your gemfile just rails?
ikke has quit [Ping timeout: 252 seconds]
<jwr>
weaksauce: yes, just rails.
<jwr>
the entire gemfile and gemfile.lock are both in my pastebin
TomyWork has quit [Quit: Leaving]
<jwr>
actually, i can reproduce it even without copying anything into a second container. i can build one container, `bundle install` will succeed, and then upon launching that same container `bundle update rails` will fail. https://pastebin.com/APzxGWpd
<jwr>
the use case for needing `bundle update` is that we do all our development in containers locally, so it's common for a deveoper to `docker exec` into a container locally and update a gem, and then push the new lockfile into our build pipeline. we don't do `bundle update` directly in prod containers or anything.
ikke has quit [Client Quit]
<adam12>
jwr: what happens if you change Gemfile do a new version of Rails, after building?
<adam12>
(then bundle update rails)
jhawthorn has quit [Ping timeout: 258 seconds]
<jwr>
when i manually change the version in the Gemfile and do `bundle update`, bundler tells me to do `bundle install --no-deployment` instead. and when i subsequently run that, it does install. https://pastebin.com/xVPBA6Bh
<jwr>
i'm not sure that changing the version in the Gemfile is a replacement for `bundle update` though, because I might just want the latest version of a gem instead of pinning a specific version in the Gemfile, and let the Gemfile.lock take care of pinning a specific one.
<weaksauce>
jwr well try that?
<weaksauce>
you are running bundle update on a specific gem version that is already installed
<weaksauce>
try installing that gem and then doing a more permissive pattern like > 6.0.3
<weaksauce>
or whatever
kwilczynski has quit []
darkxploit has quit [Quit: darkxploit]
elf_fortrez has quit [Ping timeout: 246 seconds]
<jwr>
hmm, that makes sense if maybe i was just tripping over semantic versioning. but it appears to give me the same error. https://pastebin.com/XxFTQKLw