You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using ruby-install in a Docker container to install a pinned Ruby version.
By default, ruby-installer will use wget, if it is installed, to download the source tarball. The default progress reporting option for wget is quite verbose and bloats the build log for the container.
Great idea, although I tend to not recommend using ruby-install in a Dockerfile (manually building ruby or using the official ruby docker images is probably easier). Alternatively, we should pass --quiet to wget if stdout is not a TTY? We would also need to make a similar change to the curl command.
Hi 👋 Thank you for
ruby-install
.I'm using
ruby-install
in a Docker container to install a pinned Ruby version.By default,
ruby-installer
will usewget
, if it is installed, to download the source tarball. The default progress reporting option forwget
is quite verbose and bloats the build log for the container.hadolint
, a tool for lintingDockerfile
s, suggests passing--progress=dot:giga
to limit the verbosity of wget progress updates.Would making this behavior the default or exposing a CLI switch be something suitable for this project?
Build log
Docker build log of ruby-install invocation
Example
I've added
--progress=dot:giga
elsewhere in myDockerfile
and it renders output like this:The text was updated successfully, but these errors were encountered: