Docker Image Cache When using an older ruby 1.9.3

When building Dockerfile from an older version of ruby I’m getting a docker-cache error, see my Dockerfile to reproduce this error.

FROM ruby:1.9.3-p551

# Create app directory
RUN mkdir -p /app


ENV RAILS_ENV=production
COPY . /app/
COPY Gemfile /app/
COPY Gemfile.lock /app/

RUN sed -i '/jessie-updates/d' /etc/apt/sources.list

# Install dependencies
RUN apt-get update && apt-get install -qq -y build-essential nodejs npm && apt-get install -qq -y zip

RUN bundle install
RUN mkdir -p log
RUN touch $RAILS_ENV.log
RUN cp /usr/share/zoneinfo/America/Toronto /etc/localtime
#RUN bundle exec sidekiq -d -e $RAILS_ENV -C config/sidekiq.yml -L log/$RAILS_ENV.log

ENTRYPOINT ["bundle", "exec"]

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Hi @manpreetnarang, if you are seeing this error in your App Platform builds, it is because the ruby:1.9.3-p551 image uses a deprecated v1 Docker image manifest, which is not supported by App Platform.

As a workaround you can pull the image locally and push it to your own account, which will upgrade the manifest to v2, and then update the Dockerfile FROM to use your own version of the image:

docker pull ruby:1.9.3-p551
docker tag ruby:1.9.3-p551 your-dockerhub-username/ruby:1.9.3-p551
docker push your-dockerhub-username/ruby:1.9.3-p551

Let me know if that works!


Hi there @manpreetnarang,

What is the exact docker build command that you are using? Also can you share the exact error that you are getting?

One thing that I could suggest is making sure that you have the base image in place with the docker images command.

As far as I can see it is still present on Dockerhub:

Regards, Bobby