RVM VS ruby-build

After googling it seems this is what I can find on GitHub issues which appears to be the most recent thread on the issue, or a similar issue.

rvm (probably the most used manager)

One suggestion would be to setup your install based on a development environment using git and a Ruby version manager like rvm or rbenv to allows you to setup a user controlled gemset and execution path.

If you're using rvm, then the rvm repository.

2023-04-30 03:17:03.814Z: #20 55.72 #20 55.72 WARNING: apt does not have a stable CLI interface. Use with caution in scripts. #20 55.72 #20 55.84 #20 55.84 Warning: PATH set to RVM ruby but GEM_HOME and/or GEM_PATH not set, see: #20 55.84 https://github.com/rvm/rvm/issues/3212 #20 55.84 2023-04-30 03:17:05.920Z: #20 57.89 ./install.sh: 32: Syntax error: "(" unexpected #20 57.89 ERROR: Feature "Android SDK" (ghcr.io/jarrodcolburn/features/android-sdk) failed to install! 2023-04-30 03:17:06.624Z: #20 ERROR: executor failed running [/bin/sh -c cp -ar /tmp/build-features-src/android-sdk_5 /tmp/dev-container-features && chmod -R 0755 /tmp/dev-container-features/android-sdk_5 && cd /tmp/dev-container-features/android-sdk_5 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh && rm -rf /tmp/dev-container-features/android-sdk_5]: exit code: 2 2023-04-30 03:17:06.630Z: ------ > [dev_containers_target_stage 8/9] RUN --mount=type=bind,from=dev_containers_feature_content_source,source=android-sdk_5,target=/tmp/build-features-src/android-sdk_5 cp -ar /tmp/build-features-src/android-sdk_5 /tmp/dev-container-features && chmod -R 0755 /tmp/dev-container-features/android-sdk_5 && cd /tmp/dev-container-features/android-sdk_5 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh && rm -rf /tmp/dev-container-features/android-sdk_5: #20 55.60 done. #20 55.72 #20 55.72 WARNING: apt does not have a stable CLI interface. Use with caution in scripts. #20 55.72 #20 55.84 #20 55.84 Warning: PATH set to RVM ruby but GEM_HOME and/or GEM_PATH not set, see: #20 55.84 https://github.com/rvm/rvm/issues/3212 #20 55.84 #20 57.89 ./install.sh: 32: Syntax error: "(" unexpected #20 57.89 ERROR: Feature "Android SDK" (ghcr.io/jarrodcolburn/features/android-sdk) failed to install! ------ 2023-04-30 03:17:06.633Z: ERROR: failed to solve: executor failed running [/bin/sh -c cp -ar /tmp/build-features-src/android-sdk_5 /tmp/dev-container-features && chmod -R 0755 /tmp/dev-container-features/android-sdk_5 && cd /tmp/dev-container-features/android-sdk_5 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh && rm -rf /tmp/dev-container-features/android-sdk_5]: exit code: 2 2023-04-30 03:17:06.659Z: Stop: Run: docker buildx build --load --build-context dev_containers_feature_content_source=/tmp/devcontainercli-root/container-features/0.37.0-1682824276795 --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/universal:2 --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-egnore-7f7c330024417fc1c88d19e7d01b832cf3eafa6230f5d96d870e989a2113e130-features -f /tmp/devcontainercli-root/container-features/0.37.0-1682824276795/Dockerfile.extended /var/lib/docker/codespacemount/.persistedshare/empty-folder 2023-04-30 03:17:06.664Z: {"outcome":"error","message":"Command failed: docker buildx build --load --build-context dev_containers_feature_content_source=/tmp/devcontainercli-root/container-features/0.37.0-1682824276795 --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/universal:2 --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-egnore-7f7c330024417fc1c88d19e7d01b832cf3eafa6230f5d96d870e989a2113e130-features -f /tmp/devcontainercli-root/container-features/0.37.0-1682824276795/Dockerfile.extended /var/lib/docker/codespacemount/.persistedshare/empty-folder","description":"An error occurred setting up the container."} 2023-04-30 03:17:06.671Z: Error: Command failed: docker buildx build --load --build-context dev_containers_feature_content_source=/tmp/devcontainercli-root/container-features/0.37.0-1682824276795 --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/universal:2 --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-egnore-7f7c330024417fc1c88d19e7d01b832cf3eafa6230f5d96d870e989a2113e130-features -f /tmp/devcontainercli-root/container-features/0.37.0-1682824276795/Dockerfile.extended /var/lib/docker/codespacemount/.persistedshare/empty-folder 2023-04-30 03:17:06.675Z: at wse (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:1916:3264) 2023-04-30 03:17:06.677Z: at K7 (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:1916:3200) 2023-04-30 03:17:06.679Z: at processTicksAndRejections (internal/process/task_queues.js:95:5) 2023-04-30 03:17:06.680Z: at async Hse (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:1931:2626) 2023-04-30 03:17:06.695Z: at async Ch (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:1931:3741) 2023-04-30 03:17:06.706Z: at async cae (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:2059:17376) 2023-04-30 03:17:06.715Z: at async uae (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:2059:17117) 2023-04-30 03:17:06.717Z: devcontainer process exited with exit code 1 ====================================== ERROR ==================================== 2023-04-30 03:17:06.724Z: Failed to create container. ================================================================================= 2023-04-30 03:17:06.726Z: Error: Command failed: docker buildx build --load --build-context dev_containers_feature_content_source=/tmp/devcontainercli-root/container-features/0.37.0-1682824276795 --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/universal:2 --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-egnore-7f7c330024417fc1c88d19e7d01b832cf3eafa6230f5d96d870e989a2113e130-features -f /tmp/devcontainercli-root/container-features/0.37.0-1682824276795/Dockerfile.extended /var/lib/docker/codespacemount/.persistedshare/empty-folder 2023-04-30 03:17:06.729Z: Error Code: 1302 ====================================== ERROR ==================================== 2023-04-30 03:17:06.731Z: Container creation failed. ================================================================================= 2023-04-30 03:17:06.741Z: ===================================== WARNING =================================== 2023-04-30 03:17:06.758Z: Creating recovery container. =================================================================================

For my local machine, I use RVM (head). Other options are rbenv and asdf.

You can use tools like rbenv(https://github.com/rbenv/rbenv) and rvm(https://rvm.io/) to be able install and easily switch between different ruby versions

[!] There was an error parsing \Gemfile`: No such file or directory @ rbsysopen - /Users/transformhub/Desktop/rnapp/.ruby-version. Bundler cannot continue. # from /Users/transformhub/Desktop/rnapp/Gemfile:4 # ------------------------------------------- # # You may use http://rbenv.org/ or https://rvm.io/ to install and use this version > ruby File.read(File.join(dir_, '.ruby-version')).strip # # -------------------------------------------`

It depends how you install it. If you install it globally then it will work for all your projects. Are you using rvm for ruby version and gemset management? https://rvm.io/

Let’s get started. I prefer to manage my Ruby installations on my development machine with chruby paired with ruby-install. Another outstanding set of tools is rbenv with ruby-build. I highly recommend installing Ruby with one of those two sets of tools. Follow the instructions on their project’s READMEs. For this article, I’ll be running Ruby (MRI) v3.3.0.

Seems someone was able to fix your problem with openssl installed from linuxbrew, see herehttps://github.com/rbenv/ruby-build/discussions/2199

git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build

$ git clone https://github.com/rbenv/rbenv.git ~/.rbenv $ echo 'eval "$(~/.rbenv/bin/rbenv init - bash)"' >> ~/.bashrc $ exec $SHELL $ git clone https://github.com/rbenv/ruby-build.git "$(rbenv root)"/plugins/ruby-build $ git clone https://github.com/rbenv/rbenv-vars.git "$(rbenv root)"/plugins/rbenv-vars $ rbenv install 3.2.0 $ rbenv global 3.2.0 # Test complete install with rbenv-doctor $ curl -fsSL https://github.com/rbenv/rbenv-installer/raw/main/bin/rbenv-doctor | bash $ ruby -v # Shows ruby version number if correctly installed $ gem install bundler # You might be prompted to update some gems, see command below $ gem update --system 3.4.6 # Check if this is recommended after bundler installation $ bundle -v # Shows bundler version number if correctly installed

Great! Already available via ruby-build on rbenv!

# Part One: Install basics # zlib1g-dev might be zlib-dev on Ubuntu 22.04 # lsb-release might be lsb_release on Ubuntu 22.04 sudo apt-get update && sudo apt-get -y install \ git \ ca-certificates \ curl \ gnupg \ build-essential \ lsb-release \ zlib1g-dev \ libssl-dev \ zsh && \ sh -c "$(curl -fsSL https://raw.github.com/robbyrussell/oh-my-zsh/master/tools/install.sh)" # Part Two: Installs & sets up rbenv, installs ruby git clone https://github.com/rbenv/rbenv.git ~/.rbenv && \ echo 'eval "$(~/.rbenv/bin/rbenv init - zsh)"' >> ~/.zshrc && \ source ~/.zshrc && \ git clone https://github.com/rbenv/ruby-build.git "$(rbenv root)"/plugins/ruby-build && \ rbenv install 3.1.2 && \ rbenv global 3.1.2 # Part Three: Optional minimum setup for Rails development echo "gem: --no-document" >> ~/.gemrc && \ gem install bundler && \ gem install rails

I'm using rbenv to manage Ruby versions, and it turns out they recently started building Ruby with OpenSSL 3.0 instead of OpenSSL 1.1.

ruby-build Wiki is good to learn.