Legacy Convenience Image Deprecation

Announcements
,
21

Thanks, changing the cache path to /home/circleci/go/bin/golangci-lint helped. But we also upgraded the golangci-lint version itself which created entire new keys.

22

This request is currently being tracked on CircleCI Ideas.

The Developer Hub is the source of truth for next-gen Convenience Images and what tags are available. I can definitely add a note in the OP that latest is not a thing here.

Hi, please open up an Issue on the cimg/python repo mentioning this and your use case. We can likely getting that going for newer releases of the image.

23
  1. I made a PR for Go v1.10.8. The next-gen Go image was released after this version which is why we skipped it. Please keep in mind, the new image was made with Go Modules in mind. So once that PR is reviewed and merged, Go v1.10.8 will be available but you may need to make sure you have everything in order for legacy GOPATH support. This includes placing your code in the correct directory structure within the image (GOPATH is $HOME/go.
  2. Once we release a new image for a particular version, we donā€™t publish it again. That image is a snapshot in time. If you want updates, you need to do them via apt-get, an orb, or some other fashion. Otherwise, you would move to a new image tag, such as a new Go version, to get updates from CircleCI.
  3. Customizing for images is best done with orbs. For Go, you can use the Go orb to install whatever version youā€™d like.
1 Like
24

It seems the tagging scheme for the Android images has changed from the API version, e.g. circleci/android:api-29-ndk to a time-based one, e.g. cimg/android:2022.03-ndk. Is there a conversion table or something similar? cc @FelicianoTech

25

I just added a note for Android above.

The GitHub readme for an image or the image page on the Developer Hub are the best places to get this information. Clicking a tag on the DevHub shows you whatā€™s in it. For Android that would be:

1 Like
26

No next-gen image for node-js?

27

It was one of the first released: cimg/node - CircleCI

28

Hi Feliciano,

I am working with reshmaneerukonda on `cimg/php:8.0-browsers image.
When we use this, the docker commands like docker-php-ext-configure and docker-php-ext-install could not be found as itā€™s saying it is not ubuntu based. Could you please guide us further? Thanks.

29

Hi Feliciano,

What is the next-gen image for circleci/ruby:2.7.4-buster ?

31

In the table in the original post it lists a cimg/mongo next-gen image.

I donā€™t see it listed at CircleCI Developer - Images and changing the image name in the config.yml results in the error:

Error pulling image cimg/mongo: Error response from daemon: pull access denied for cimg/mongo, repository does not exist or may require ā€˜docker loginā€™: denied: requested access to the resource is deniedā€¦ retrying
image cache not found on this host, downloading cimg/mongo

Legacy Image Next-Gen Image

circleci/mongo cimg/mongo

Should the Next-Gen image just be ā€œmongoā€ ?

32

Correct. Thank you for pointing that out, fixed.

33

cimg/ruby:2.7.4

34

Whatā€™s the next-gen image for buildpack-deps:trusty ? I tried using cimg/base and that didnā€™t work for me.

35

Hello folks, because I got a warning about deprecated images usage in CircleCI dashboard while I was checking a build, I read this guide and tried to upgrade our images from:

orbs:
  go: circleci/go@1.7.1
  docker: circleci/docker@1.0.0
  aws-ecr: circleci/aws-ecr@7.2.0
  aws-ecs: circleci/aws-ecs@1.1.0
  aws-cli: circleci/aws-cli@2.0.3
  jq: circleci/jq@2.0.1
  slack: circleci/slack@2.2.0

to

orbs:
  go: cimg/go@1.18
  docker: cimg/docker@1.0.0
  aws-ecr: cimg/aws-ecr@7.2.0
  aws-ecs: cimg/aws-ecs@1.1.0
  aws-cli: cimg/aws-cli@2.0.3
  jq: cimg/jq@2.0.1
  slack: cimg/slack@2.2.0

but when I run the build, it fails with:

# Cannot find cimg/go@1.18 in the orb registry. Check that the namespace, orb name and version are correct.
# Cannot find cimg/docker@1.0.0 in the orb registry. Check that the namespace, orb name and version are correct.
# Cannot find cimg/aws-ecr@7.2.0 in the orb registry. Check that the namespace, orb name and version are correct.
# Cannot find cimg/aws-ecs@1.1.0 in the orb registry. Check that the namespace, orb name and version are correct.
# Cannot find cimg/aws-cli@2.0.3 in the orb registry. Check that the namespace, orb name and version are correct.
# Cannot find cimg/jq@2.0.1 in the orb registry. Check that the namespace, orb name and version are correct.
# Cannot find cimg/slack@2.2.0 in the orb registry. Check that the namespace, orb name and version are correct.

Iā€™m quite confused and Iā€™m not sure I understood how to upgrade these images. Can you help me with this, please? Thanks

UPDATE: I got confused and renamed orbs too (but itā€™s fair to say that itā€™s also confusing to have circleci for orbs and cimg for Docker images), but I get an error even for Docker images.

I renamed this:

- image: circleci/dynamodb

to this:

- image: cimg/dynamodb

and I get this error:

Error pulling image cimg/dynamodb: Error response from daemon: pull access denied for cimg/dynamodb, repository does not exist or may require 'docker login': denied: requested access to the resource is denied... retrying
  image cache not found on this host, downloading cimg/dynamodb

so at this point I really donā€™t know why the dashboard is telling me to upgrade images if the new names are not correct.

36

What should be the steps to checkout mongodb next-gen image

Article shows steps for jruby only.