[{"_1":2,"_130":-5,"_131":-5},"loaderData",{"_3":4,"_13":14,"_19":20,"_124":125},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17},"username","isAskGordonEnabled",true,"isUsingNewTemplate","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)",{"_21":22,"_23":24,"_53":54,"_55":-7,"_56":-7,"_57":-7,"_58":-7,"_46":59,"_115":17,"_83":84,"_116":82,"_117":45,"_29":30,"_118":11,"_119":11,"_120":121,"_122":-5,"_123":11},"scanningType","none","tagData",{"_25":26,"_27":28,"_29":30,"_31":32,"_33":34,"_35":36,"_37":38,"_39":28,"_40":41,"_42":43,"_44":45,"_46":47,"_48":-5,"_49":38,"_50":51,"_52":17},"content_type","image","creator",35095401,"digest","sha256:e1ec68ae75651270a142981f583b034e4c257564fbde097a877b30146f3dabc2","full_size",10086,"id",1258397780,"images",[],"last_updated","2026-08-04T06:31:12.621735Z","last_updater","last_updater_username","bitnamibot508","media_type","application/vnd.oci.image.config.v1+json","name","sha256-c2ea6af6c9ec84465d630087b3934687d583bece2c0d71d2dad95246f6159d95.att","repository",230166,"tag_last_pulled","tag_last_pushed","tag_status","active","v2","tagImages",[],"layerOrdinals","packageName","cveId","sbom",{"_60":61,"_66":67,"_69":70,"_71":72,"_73":11,"_37":74,"_75":76,"_77":78,"_44":82,"_83":84,"_85":86,"_87":26,"_88":89,"_90":91,"_92":51,"_93":-5,"_94":95,"_96":97,"_98":11,"_99":84,"_100":101,"_106":17,"_107":108,"_112":84,"_113":114},"categories",[62],{"_44":63,"_64":65},"Languages & frameworks","slug","languages-and-frameworks","content_types",[26,68],"unrecognized","date_registered","2015-06-17T01:24:29.512152Z","description","Bitnami Secure Image for ruby","is_private","2026-08-08T11:26:07.619444Z","last_modified","2026-03-03T12:29:36.816474Z","media_types",[79,43,80,81],"application/vnd.docker.distribution.manifest.list.v2+json","application/vnd.oci.image.index.v1+json","application/vnd.vmware.tac.metadata.config.v1+json","ruby","namespace","bitnami","pull_count",28272326,"repository_type","star_count",24,"status",1,"status_description","source","collaborator_count",0,"full_description","# Bitnami Secure Image for Ruby\n\n> Ruby on Rails is a full-stack development environment optimized for programmer happiness and sustainable productivity. It lets you write beautiful code by favoring convention over configuration.\n\n[Overview of Ruby](https://www.ruby-lang.org)\nTrademarks: This software listing is packaged by Bitnami. The respective trademarks mentioned in the offering are owned by the respective companies, and use of them does not imply any affiliation or endorsement.\n\n## TL;DR\n\n```console\ndocker run --name ruby REGISTRY_NAME/bitnami/ruby:latest\n```\n\n> Note: You need to substitute the `REGISTRY_NAME` placeholder with a reference to your container registry.\n\n## Choosing between the _Standard_ and _Minimal_ image\n\nThis asset is available in two flavors: _Standard_ and _Minimal_; designed to address different use cases and operational needs.\n\n### Standard images\n\nThe standard images are full-featured, production-ready containers built on top of secure base operating systems. They include:\n\n- The complete runtime and commonly used system tools.\n- A familiar Linux environment (shell, package manager, debugging utilities).\n- Full compatibility with most CI/CD pipelines and existing workloads.\n\nRecommended for:\n\n- Development and testing environments.\n- Workloads requiring package installation or debugging tools.\n- Applications that depend on system utilities or shared libraries.\n\n### Minimal images\n\nThe minimal images are optimized, distroless-style containers derived from a stripped-down base. They only ship what’s strictly necessary to run the application; no shell, package manager, or extra libraries. They provide:\n\n- Smaller size: Faster pull and startup times.\n- Reduced attack surface: Fewer components and potential vulnerabilities.\n- Simpler maintenance: Fewer dependencies to patch or update.\n\nRecommended for:\n\n- Production environments prioritizing performance and security.\n- Regulated or security-sensitive workloads\n- Containers built via multi-stage builds (e.g., Golang static binaries).\n\n## Supported tags and respective `Dockerfile` links\n\nLearn more about the Bitnami tagging policy and the difference between rolling tags and immutable tags [in our documentation page](https://techdocs.broadcom.com/us/en/vmware-tanzu/application-catalog/tanzu-application-catalog/services/tac-doc/apps-tutorials-understand-rolling-tags-containers-index.html).\n\n### Deprecation Note (2022-01-21)\n\nThe `prod` tags has been removed; from now on just the regular container images will be released.\n\n### Deprecation Note (2020-08-18)\n\nThe formatting convention for `prod` tags has been changed:\n\n- `BRANCH-debian-10-prod` is now tagged as `BRANCH-prod-debian-10`\n- `VERSION-debian-10-rX-prod` is now tagged as `VERSION-prod-debian-10-rX`\n- `latest-prod` is now deprecated\n\n## Get this image\n\nThe recommended way to get the Bitnami Ruby Docker Image is to pull the prebuilt image from the [Docker Hub Registry](https://hub.docker.com/r/bitnami/ruby).\n\n```console\ndocker pull REGISTRY_NAME/bitnami/ruby:latest\n```\n\nTo use a specific version, you can pull a versioned tag. You can view the [list of available versions](https://hub.docker.com/r/bitnami/ruby/tags/) in the Docker Hub Registry.\n\n```console\ndocker pull REGISTRY_NAME/bitnami/ruby:[TAG]\n```\n\nIf you wish, you can also build the image yourself by cloning the repository, changing to the directory containing the Dockerfile and executing the `docker build` command. Remember to replace the `APP`, `VERSION` and `OPERATING-SYSTEM` path placeholders in the example command below with the correct values.\n\n```console\ngit clone https://github.com/bitnami/containers.git\ncd bitnami/APP/VERSION/OPERATING-SYSTEM\ndocker build -t REGISTRY_NAME/bitnami/APP:latest .\n```\n\n## Using `docker-compose.yaml`\n\nPlease be aware this file has not undergone internal testing. Consequently, we advise its use exclusively for development or testing purposes.\n\n## Entering the REPL\n\nBy default, running this image will drop you into the Ruby REPL (`irb`), where you can interactively test and try things out in Ruby.\n\n```console\ndocker run -it --name ruby REGISTRY_NAME/bitnami/ruby:latest\n```\n\n**Further Reading:**\n\n- [Ruby IRB Documentation](http://ruby-doc.org/stdlib-2.4.0/libdoc/irb/rdoc/IRB.html)\n\n## Configuration\n\nThe following section describes how to run commands\n\n### Running your Ruby script\n\nThe default work directory for the Ruby image is `/app`. You can mount a folder from your host here that includes your Ruby script, and run it normally using the `ruby` command.\n\n```console\ndocker run -it --name ruby -v /path/to/app:/app REGISTRY_NAME/bitnami/ruby:latest \\\n ruby script.rb\n```\n\n### Running a Ruby app with gems\n\nIf your Ruby app has a `Gemfile` defining your app's dependencies and start script, you can install the dependencies before running your app.\n\n```console\ndocker run -it --name ruby -v /path/to/app:/app REGISTRY_NAME/bitnami/ruby:latest \\\n sh -c \"bundle install && ruby script.rb\"\n```\n\nor by modifying the [`docker-compose.yml`](https://github.com/bitnami/containers/blob/main/bitnami/ruby/docker-compose.yml) file present in this repository:\n\n```yaml\nruby:\n ...\n command: \"sh -c 'bundle install && ruby script.rb'\"\n volumes:\n - .:/app\n ...\n```\n\n**Further Reading:**\n\n- [rubygems.org](https://rubygems.org/)\n- [bundler.io](http://bundler.io/)\n\n### Accessing a Ruby app running a web server\n\nThis image exposes port `3000` in the container, so you should ensure that your web server is binding to port `3000`, as well as listening on `0.0.0.0` to accept remote connections from your host.\n\nBelow is an example of a [Sinatra](http://www.sinatrarb.com/) app listening to remote connections on port `3000`:\n\n```ruby\nrequire 'sinatra'\n\nset :bind, '0.0.0.0'\nset :port, 3000\n\nget '/hi' do\n \"Hello World!\"\nend\n```\n\nTo access your web server from your host machine you can ask Docker to map a random port on your host to port `3000` inside the container.\n\n```console\ndocker run -it --name ruby -P REGISTRY_NAME/bitnami/ruby:latest\n```\n\nRun `docker port` to determine the random port Docker assigned.\n\n```console\n$ docker port ruby\n3000/tcp -> 0.0.0.0:32769\n```\n\nYou can also manually specify the port you want forwarded from your host to the container.\n\n```console\ndocker run -it --name ruby -p 8080:3000 REGISTRY_NAME/bitnami/ruby:latest\n```\n\nAccess your web server in the browser by navigating to `http://localhost:8080`.\n\n### FIPS configuration in Bitnami Secure Images\n\nThe Bitnami Ruby Docker image from the [Bitnami Secure Images](https://go-vmware.broadcom.com/contact-us) catalog includes extra features and settings to configure the container with FIPS capabilities. You can configure the next environment variables:\n\n- `OPENSSL_FIPS`: whether OpenSSL runs in FIPS mode or not. `yes` (default), `no`.\n\n## Connecting to other containers\n\nIf you want to connect to your Ruby web server inside another container, you can use docker networking to create a network and attach all the containers to that network.\n\n### Serving your Ruby app through an nginx frontend\n\nWe may want to make our Ruby web server only accessible via an nginx web server. Doing so will allow us to setup more complex configuration, serve static assets using nginx, load balance to different Ruby instances, etc.\n\n#### Step 1: Create a network\n\n```console\ndocker network create app-tier --driver bridge\n```\n\nor using Docker Compose:\n\n```yaml\nversion: '2'\n\nnetworks:\n app-tier:\n driver: bridge\n```\n\n#### Step 2: Create a virtual host\n\nLet's create an nginx virtual host to reverse proxy to our Ruby container.\n\n```nginx\nserver {\n listen 0.0.0.0:80;\n server_name yourapp.com;\n\n location / {\n proxy_set_header X-Real-IP $remote_addr;\n proxy_set_header HOST $http_host;\n proxy_set_header X-NginX-Proxy true;\n\n # proxy_pass http://[your_ruby_container_link_alias]:3000;\n proxy_pass http://myapp:3000;\n proxy_redirect off;\n }\n}\n```\n\nNotice we've substituted the link alias name `myapp`, we will use the same name when creating the container.\n\nCopy the virtual host above, saving the file somewhere on your host. We will mount it as a volume in our nginx container.\n\n#### Step 3: Run the Ruby image with a specific name\n\n```console\ndocker run -it --name myapp \\\n --network app-tier \\\n -v /path/to/app:/app \\\n REGISTRY_NAME/bitnami/ruby:latest ruby script.rb\n```\n\nor using Docker Compose:\n\n```yaml\nversion: '2'\nmyapp:\n image: REGISTRY_NAME/bitnami/ruby:latest\n command: ruby script.rb\n networks:\n - app-tier\n volumes:\n - .:/app\n```\n\n#### Step 4: Run the nginx image\n\n```console\ndocker run -it \\\n -v /path/to/vhost.conf:/bitnami/nginx/conf/vhosts/yourapp.conf \\\n --network app-tier \\\n REGISTRY_NAME/bitnami/nginx:latest\n```\n\nor using Docker Compose:\n\n```yaml\nversion: '2'\nnginx:\n image: REGISTRY_NAME/bitnami/nginx:latest\n networks:\n - app-tier\n volumes:\n - /path/to/vhost.conf:/bitnami/nginx/conf/vhosts/yourapp.conf\n```\n\n## Notable Changes\n\n### 2.3.1-r0 (2016-05-11)\n\n- Commands are now executed as the `root` user. Use the `--user` argument to switch to another user or change to the required user using `sudo` to launch applications. Alternatively, as of Docker 1.10 User Namespaces are supported by the docker daemon. Refer to the [daemon user namespace options](https://docs.docker.com/engine/security/userns-remap/) for more details.\n\n### 2.2.3-0-r02 (2015-09-30)\n\n- `/app` directory no longer exported as a volume. This caused problems when building on top of the image, since changes in the volume were not persisted between RUN commands. To keep the previous behavior (so that you can mount the volume in another container), create the container with the `-v /app` option.\n\n### 2.2.3-0-r01 (2015-08-26)\n\n- Permissions fixed so `bitnami` user can install gems without needing `sudo`.\n\n## License\n\nCopyright © 2026 Broadcom. The term \"Broadcom\" refers to Broadcom Inc. and/or its subsidiaries.\n\nLicensed under the Apache License, Version 2.0 (the \"License\");\nyou may not use this file except in compliance with the License.\nYou may obtain a copy of the License at\n\n\n\nUnless required by applicable law or agreed to in writing, software\ndistributed under the License is distributed on an \"AS IS\" BASIS,\nWITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\nSee the License for the specific language governing permissions and\nlimitations under the License.\n","has_starred","hub_user","immutable_tags_settings",{"_102":11,"_103":104},"enabled","rules",[105],".*","is_automated","permissions",{"_109":17,"_110":11,"_111":11},"read","write","admin","user","storage_size",2806517996407,"isOrg","reponame","tag","canDeleteTags","isHubSbxKitsEnabled","currentTab","","tagAttestations","displaySecurityMetadata","routes/_layout.layers.$namespace.$reponame.$tag.(images).($imageUrlDigest)._index",{"_21":22,"_57":-7,"_55":-7,"_56":-7,"_23":126,"_29":30,"_128":-7,"_129":11},{"_25":26,"_27":28,"_29":30,"_31":32,"_33":34,"_35":127,"_37":38,"_39":28,"_40":41,"_42":43,"_44":45,"_46":47,"_48":-5,"_49":38,"_50":51,"_52":17},[],"imageWithLayers","hasPermissionToViewRepoSettings","actionData","errors"]

Help

System theme

Docker Suite

bitnami/ruby:sha256-c2ea6af6c9ec84465d630087b3934687d583bece2c0d71d2dad95246f6159d95.att