Ruby minor version is not frozen in the container image about passenger-docker HOT 9 CLOSED

Having the same issue.

from passenger-docker.

Also having this issue. Looked around the Brightbox APT (https://launchpad.net/~brightbox/+archive/ubuntu/ruby-ng) and it only appears to include the most recent minor version.

from passenger-docker.

That is correct. There's not much we can do about it. There is no way to lock down to a specific version when using Launchpad's repositories

from passenger-docker.

Would it make sense to remove the Brightbox dependency and instead install from source?

from passenger-docker.

Perhaps. Something to be considered for the future.

from passenger-docker.

Could you give an example of how you use this image without the locking ability? I think I'm doing something wrong. My projects fail as soon as the minor version is bumped. We rebuild the image as part of our CI system.

from passenger-docker.

If you're building passenger-docker from scratch (as in, you forked this repository and used our Dockerfile) then I'm afraid there's no way to lock down to a specific Ruby teeny version.

If you build on top of the images we supply, then you can just lock down to a specific passenger-docker version. However, if you run apt-get upgrade inside your own container, that that can still change the Ruby version. In that case, you can setup an apt-get hold to prevent apt-get upgrade from upgrading Ruby.

from passenger-docker.

You're right! I forgot that using the FROM declarative actually downloads the image from the hub instead of just executing that particular versions Dockerfile.

Thanks

from passenger-docker.

no longer relevant we use rvm now, closing

from passenger-docker.