Thank you very much for your reply.
Upon updating the aws-ecr orb version to 9.0.3, I encountered the following error message:
Error calling workflow: ‘build_and_push_image’
Cannot find a definition for job named aws-ecr/build-and-push-image
My issue has been resolved.
Find below my updated config.yml file
version: 2.1
orbs:
aws-ecr: circleci/aws-ecr@7.0.0
aws-ecs: circleci/aws-ecs@2.2.1
executors:
default-ubuntu:
machine:
image: ubuntu-2004:current
workflows:
build_and_push_image:
jobs:
- aws-ecr/build-and-push-image:
executor: default-ubuntu
context: AWS
repo: live-data-test
tag: "latest"
dockerfile: Dockerfile
path: .
filters:
branches:
only: main
- aws-ecs/deploy-service-update:
context: AWS
cluster-name: 'SQA'
container-image-name-updates: 'container=live-data-test, tag=latest'
family: 'live-data-test'
requires:
- aws-ecr/build-and-push-image
1 Like
Hi,
I have a similar case I believe in which we use cimg/python:3.9 at best last modified: Aug 25, 2023 which underneath I believe uses to be deprecated ubuntu-2204:2022.04.2 while latest available is 2022.04.3
Can you provide upgrade to cimg/python:3.9 as you did for aws cli?
Hi @zajacmp3,
cimg/python3.9 is a docker image so you might be having issues do to another part of your config. I am wondering if you are using remote docker?
Yes you are correct. I’ve found numerous usages of setup remote docker with deprecated versions like: version: 20.10.12 (and a lot of older ones)
I know now how to tackle this. Thank you
we are using it via docker
Hello team,
I have encountered an error
FAILURE: Build failed with an exception.
- What went wrong:
Execution failed for task ‘:compileKotlin’.
Could not resolve all files for configuration ‘:compileClasspath’.
Could not find au.com.console:kotlin-jpa-specification-dsl:2.0.0.
Required by:
project :
- Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
However I got a suggestion that I’m using deprecated image ‘ubuntu-2004:202010-01’. It’s advised to switch to a more recent image so I have changed to ‘ubuntu-2004:current’ however now we are getting error in gradle stage with the same error.
PFB code :
version: 2.1
orbs:
aws-ecr: circleci/aws-ecr@7.0.0
aws-ecs: circleci/aws-ecs@02.2.1
slack: circleci/slack@4.1
jobs:
gradle_build_and_test:
machine:
image: ubuntu-2004:current
steps:
- trigger_slack_notification
- install_openjdk
- checkout
- with_cache:
Hello team,
I have encountered an error
FAILURE: Build failed with an exception.
- What went wrong:
Execution failed for task ‘:compileKotlin’.
Could not resolve all files for configuration ‘:compileClasspath’.
Could not find au.com.console:kotlin-jpa-specification-dsl:2.0.0.
Required by:
project :
- Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
However I got a suggestion that I’m using deprecated image ‘ubuntu-2004:202010-01’. It’s advised to switch to a more recent image so I have changed to ‘ubuntu-2004:current’ however now we are getting error in gradle stage with the same error.
PFB code :
version: 2.1
orbs:
aws-ecr: circleci/aws-ecr@7.0.0
aws-ecs: circleci/aws-ecs@02.2.1
slack: circleci/slack@4.1
jobs:
gradle_build_and_test:
machine:
image: ubuntu-2004:current
steps:
- trigger_slack_notification
- install_openjdk
- checkout
- with_cache:
Hello @vishalkotha95
It looks like you’re having some problems with your Kotlin code compiling. Since you are seeing issues on both the deprecated and current machine images, I would first investigate issues related to your particular project dependancies - it looks like you’re having problems with Gradle finding kotlin-jpa-specification-dsl:2.0.0 from maven - before considering issues with the change in machine image.
I have tried in my local it is working fine, may be the maven repository access issue (kotlin-jpa-specification-dsl:2.0.0) from the build server is failing. Request you to please check. JFrog
@vishalkotha95 I’m not sure that this discussion forum post is applicable to the issues you’re having - this post is related to the brown outs of the old deprecated Linux machines and issues related to upgrading images in particular.
That said, If you want to debug this issue further I suggest re-running your job with SSH and logging into the job in question so that you can run whatever commands you want in order to test things interactively. This should allow you to determine how the environment in CI differs from your local setup.
HTH
Mark.
FYI, the guidance at the top of the thread is a bit confusing or misleading because it says default and edge are both valid tags, and it provides an example of using a tag as a suffix (ubuntu-2204:edge). However, when I tried using default as a suffix, I got this message:
Job was rejected because resource class large, image ubuntu-2004:default is not a valid resource class
The CircleCI Linux VM images support policy page under “Tagging” has the same issue because it includes default at the top of the list of tags, but it doesn’t say which tags can be used as suffixes and which can only be used in standalone fashion.
My suggestion: instead of saying just–
defaultcurrent- etc.
How about saying something like–
default[image-name]:current- etc.
That way it’s clear how the tags can be used. (Or maybe some tags can be used in both forms – I’m not sure.)
Hi everyone,
I have a question about Docker images. I’m using this Docker image for my CI: [cimg/ruby:2.7], which is based on Ubuntu 20.04. Do we need to update this, or will just the orb stop working?
1 Like
We are using the linux images since 1 month everything seems good, however from today morning we are getting an error stating we are using old linux image and the build is fail, however I have rechecked it is using new. PFB screenshots
Hello! Did your build start failing? We may be encountering a similar issue using cimg/ruby:3.1.2-browsers based on Ubuntu 20.04.6.