Thanks @kojima-takeo & @rmoskal for reporting the issue. We are investigating the issue and update here with fix as soon as possible. Meanwhile, could you please try using the below code for installing GCSFuse in your Ubuntu/Debian based Dockerfile:

ENV GCSFUSE_VERSION=1.2.0

RUN apt-get update -y && \
    curl -LJO "https://github.com/GoogleCloudPlatform/gcsfuse/releases/download/v${GCSFUSE_VERSION}/gcsfuse_${GCSFUSE_VERSION}_amd64.deb" && \
    apt-get -y install fuse && \
    apt-get clean && \
    dpkg -i "gcsfuse_${GCSFUSE_VERSION}_amd64.deb"

@kojima-takeo for your use-case, the Dockerfile mentioned in https://github.com/GoogleCloudPlatform/gcsfuse/issues/1424#issue-1927877132 would look like:

# Use the official lightweight Python image.
# https://hub.docker.com/_/python
FROM python:3.11-buster

# Install system dependencies
ENV GCSFUSE_VERSION=1.2.0

RUN apt-get update -y && \
    curl -LJO "https://github.com/GoogleCloudPlatform/gcsfuse/releases/download/v${GCSFUSE_VERSION}/gcsfuse_${GCSFUSE_VERSION}_amd64.deb" && \
    apt-get -y install fuse tini && \
    apt-get clean && \
    dpkg -i "gcsfuse_${GCSFUSE_VERSION}_amd64.deb"

# Set fallback mount directory
ENV MNT_DIR /mnt/gcs

# Copy local code to the container image.
ENV APP_HOME /app
WORKDIR $APP_HOME
COPY . ./

# Install production dependencies.
RUN pip install -r requirements.txt

# Ensure the script is executable
RUN chmod +x /app/gcsfuse_run.sh

# Use tini to manage zombie processes and signal forwarding
# https://github.com/krallin/tini
ENTRYPOINT ["/usr/bin/tini", "--"]

# Pass the startup script as arguments to Tini
CMD ["/app/gcsfuse_run.sh"]

Please reach out if you face issues with above installations.

http -> https is working! http://packages.cloud.google.com/apt -> https://packages.cloud.google.com/apt ~

Install gcsfuse

RUN apt-get update && apt-get install -y curl gnupg lsb-release RUN echo “deb https://packages.cloud.google.com/apt gcsfuse-buster main” > /etc/apt/sources.list.d/gcsfuse.list RUN curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | apt-key add - RUN apt-get update && apt-get install -y gcsfuse

Hey @jaakkom & @aamarques . Apologies for the inconvenience here. The problem is arising due to use of “http://packages.cloud.google.com/” instead of “https://packages.cloud.google.com/” in cloud run’s document for installation of GCSFuse (e.g. Node.js Dockerfile).

We are working to get the Cloud run documents updated with the correct and official installation command i.e. (https://cloud.google.com/storage/docs/gcsfuse-install). e.g. we have updated the Python Dockerfile.

Meanwhile, we suggest to use the officially documented installation commands (https://cloud.google.com/storage/docs/gcsfuse-install) or the workarounds mentioned in this issue.

This fixed it for me: -RUN echo “deb http://packages.cloud.google.com/apt gcsfuse-bionic main” | tee /etc/apt/sources.list.d/gcsfuse.list +RUN echo “deb https://packages.cloud.google.com/apt gcsfuse-bionic main” | tee /etc/apt/sources.list.d/gcsfuse.list

@rmoskal Thank you for sharing your experience, and I appreciate the suggestion to rephrase the issue to highlight the problem with installing gcsfuse from the repo. It seems like this is a recent occurrence as the Dockerfile worked perfectly up until a week ago, with the issue starting around 2-3 days ago.

I share your surprise regarding the lack of widespread discussion on this matter, which may indeed suggest a limited number of users mounting GCS on Cloud Run with gcsfuse. However, the impact is significant for those of us relying on this setup for our applications.

I hope this issue gains the necessary attention for a prompt resolution. In the meantime, if anyone has discovered a workaround or alternative approach to mount GCS on Cloud Run, sharing it here would be immensely beneficial. Thank you again for your input and shared concern.

This should more likely be called, unable to install gcsFuse from the repo. In any case it’s happening to me as well, and is breaking my ability to deploy workloads based on the docker image. I’m surprisedf the internet is not BLOWING up about this!

Dear @sethiay

Thank you for your continuous support and insight. It was indeed a very basic oversight on my part. I have confirmed that the original code also installs curl. After applying your suggested code once again, I was able to successfully deploy. Your guidance has been invaluable, and I am deeply appreciative.

Thank you for the persistent support which has enabled me to deploy after a week, and I am looking forward to the progression of the project with great anticipation.

Best regards,