Hi,
We are in the process of migration to kubernetes runners and there is a strange behavior when I use our own copy of plugins/ecr
image. This is a 1:1 copy from the version on dockerhub, we just keep it in our ECR repo.
The following step is used for image building and pushing:
local buildPushImage(env, tag) = {
name: 'build_push_image_%(env)s' % { env: env},
image: 'ACCOUNT_ID.dkr.ecr.us-east-1.amazonaws.com/public/plugins/ecr:latest',
pull: 'if-not-exists',
settings: {
repo: 'ACCOUNT_ID.dkr.ecr.us-east-1.amazonaws.com/flybox/dip-cdc',
registery: 'ACCOUNT_ID.dkr.ecr.us-east-1.amazonaws.com',
region: 'us-east-1',
repository_policy: 'ecr_repository_policy.json',
tags: [
'latest',
tag
],
},
environment: {
PLUGIN_CREATE_REPOSITORY: true,
PLUGIN_PULL_IMAGE: false,
},
};
This results in the classic error Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Now when I change the image URL to:
image: 'plugins/ecr:latest',
everything works and the build is proceeding.
Should we mount that /var/run folder? I removed those lines in the k8s runner migration process and seems like it is redundant.
Any help would be appreciated,
Erez