Using ruby's official image on Dockerfile #55
Conversation
alaxalves
changed the title
|
But why?
Debian gives us very long support. They actually backport security
patches. I'm in favor of sticking to Debian where possible, unless
there's a compelling reason to switch.
El dom, 7 de jun de 2020 a las 12:47, Álax de Carvalho Alves
<[email protected]> escribió:
… Fixes #54
<#54>
You can view, comment on, or merge this pull request online at:
<#55>
Commit Summary
Using ruby's official image on Dockerfile
File Changes
*M* Dockerfile
<https://github.com/publiclab/mapknitter-exporter-sinatra/pull/55/files#diff-3254677a7917c6c01f55212f86c57fbf>
(4)
Patch Links:
<https://github.com/publiclab/mapknitter-exporter-sinatra/pull/55.patch>
<https://github.com/publiclab/mapknitter-exporter-sinatra/pull/55.diff>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#55>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABQYSYGT3HDZCTZKZOFLSTRVPVGXANCNFSM4NXSPFHA>.
|
Debian's raw image comes with several packages we don't need besides requiring the need for us to install ruby* packages in it. If we use a |
|
In here we wouldn't stop using Debian Buster, we just take advantage of it by setting a ruby image set on top of a debian buster image. |
alaxalves
changed the title
|
Hmm. Does @alaxalves are there any cons you can think of so we can understand any tradeoffs well? Thank you both for thoroughness! |
|
Just wondering if you'd had a moment to think on this, @alaxalves ! Thanks a ton!!! |
I'll do this for sure. I just had been focusing on other activities lately |
|
The backport supporting is the same, the Ruby community is as wide as the Debian community. I'm closing this since it feels it does not aggregate much for the project |
|
Thanks, Alax! Appreciate it! |
Fixes #54
I'd like to get #58 merged before merging this, since we'll be able to test this out more properly.