Skip to content

Conversation

kumaripuja-ssk
Copy link

  • Updated URLs in Docker file as per the requirement.
  • Related Buganizer: http://b/433251254

@kumaripuja-ssk kumaripuja-ssk requested review from a team as code owners July 25, 2025 14:40
@product-auto-label product-auto-label bot added the samples Issues that are directly related to samples. label Jul 25, 2025
@glasnt glasnt changed the title GSP943-lab-updates fix(rails): update Dockerfile Jul 27, 2025
Comment on lines -24 to +41
bundle config set --local deployment 'true' && \
bundle config set --local without 'development test' && \
bundle install
bundle config set --local deployment 'true' && \
bundle config set --local without 'development test' && \
bundle install
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: It's useful when using command continuations to use indenting to make it clear that this is all one layer, one run command.

Please apply to other commands.

echo "deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_20.x buster main" > \
/etc/apt/sources.list.d/nodesource.list && \
apt-get update && \
apt-get install -y nodejs lsb-release
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: it would make more sense to install the lsb-release package in the same step that the repository is setup

# [START cloudrun_rails_base_image]
# Pinning the OS to buster because the nodejs install script is buster-specific.
# Be sure to update the nodejs install command if the base image OS is updated.
FROM ruby:3.2-buster
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question: if there's an issue with buster, why not update the base image to bookworm? Does that version have the same issue?

@glasnt glasnt added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 27, 2025
@kokoro-team kokoro-team removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jul 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

samples Issues that are directly related to samples.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants