Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drop docker hub support #2103

Closed
chenrui333 opened this issue Mar 2, 2022 · 6 comments
Closed

Drop docker hub support #2103

chenrui333 opened this issue Mar 2, 2022 · 6 comments

Comments

@chenrui333
Copy link
Member

👋 with the recent fixes for docker multiplatform image builds, we have also removed the docker hub support via circleci starting release 0.18.4.

Let me know if you have any questions or concerns, thanks!

@chenrui333 chenrui333 pinned this issue Mar 2, 2022
@dgteixeira
Copy link

dgteixeira commented Mar 3, 2022

EDIT: Detailed our terraform resource when applying the atlantis helm chart for the most recent version

@chenrui333 hey!
I have a question.

Using helm chart v3.15.5, documented here, how can we change the container registry (from the apparent default being docker hub) to ghcr ?

With the following config on the helm chart:

resource "helm_release" "atlantis" {
  name             = "atlantis"
  repository       = "https://runatlantis.github.io/helm-charts"
  chart            = "atlantis"
  version          = "3.15.5"
  namespace        = "atlantis"
  wait_for_jobs    = true
  create_namespace = false
  values = [
    <<YAML

  image:
    repository: runatlantis/atlantis
    tag: v0.18.5

  hidePrevPlanComments: true

  defaultTFVersion: 1.1.7

  resources:
    limits:
      cpu: 3000m
      memory: 1Gi
    requests:
      cpu: 3000m
      memory: ${terraform.workspace == "staging" ? "256Mi" : "1Gi"}

  nodeSelector:
    cloud.google.com/gke-nodepool: ${var.atlantis_node_pool_name}

  tolerations:
  - key: "dedicated"
    value: "atlantis"
    operator: "Equal"
    effect: "NoSchedule"
  YAML
  ]
  depends_on = [
    kubectl_manifest.atlantis
  ]
}

We are getting the error:

Warning Failed 18m (x4 over 20m) kubelet Failed to pull image "runatlantis/atlantis:v0.18.5": rpc error: code = NotFound desc = failed to pull and unpack ima "docker.io/runatlantis/atlantis:v0.18.5": failed to resolve reference "docker.io/runatlantis/atlantis:v0.18.5": docker.io/runatlantis/atlantis:v0.18.5: not found

Since this is no longer supported, shouldn't the default endpoint also be changed to ghcr?

Thanks!

@dgteixeira
Copy link

dgteixeira commented Mar 3, 2022

EDIT: Created the issue in atlantis for default repo helm chart change.
@chenrui333, we fixed it by adding the ghcr.io prefix to the repository.

As follows:

  image:
    repository: ghcr.io/runatlantis/atlantis
    tag: v0.18.5

This works like a charm!

However, as stated in the previous comment, if docker.io is not supported, shouldn't be as the default repository in the helm chart. I opened the issue: #2110

@chenrui333
Copy link
Member Author

Thanks for reporting, it let me update the default one.

@marceloboeira
Copy link
Contributor

@chenrui333 I've updated a few broken references in the docs

blairdrummond added a commit to liatrio/builder-images that referenced this issue May 23, 2022
Dockerhub Support is being dropped runatlantis/atlantis#2103
New package versions are on ghcr.io (github registry)

Bumped the terragrunt and atlantis versions to the newest available
minor version. Unfortuntely the images are still vulnerable and more
complex remediations may be needed.
blairdrummond added a commit to liatrio/builder-images that referenced this issue May 24, 2022
* fix(builder-image-aws): update alpine to 3.15

* feat(atlantis-image): move to ghcr.io, bump versions

Dockerhub Support is being dropped runatlantis/atlantis#2103
New package versions are on ghcr.io (github registry)

Bumped the terragrunt and atlantis versions to the newest available
minor version. Unfortuntely the images are still vulnerable and more
complex remediations may be needed.

* chore(builder-image-azure-terraform): clean apt lists

As per the guidance in [docker's apt-get](https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#apt-get) docs,
clean up the apt lists after apt updates.

* chore(builder-image-azure-terraform): switch debian base to ubuntu

`trivy image debian:buster-slim` has never given me less than half a dozen critical CVEs.
It's always full of critical CVEs. The ubuntu images tend to be pretty much compatible, but usually CVE free.

* chore(builder-image-azure-terraform): bump package versions

* chore(builder-image-gitty-up): bump alpine version

* chore(builder-image-goreleaser): bump goreleaser to 1.9.1, bump alpine

* chore(builder-image-gradle): bump gradle version

Note that there is a remaining CVE associated to a third-party oauth
library. That is being tracked in the gradle project

gradle/gradle#20468

* chore(builder-image-maven): bump maven, fix apt layering

* chore(builder-image-openshift): bump helm to v3 and bump alpine

* chore(builder-image-ruby): bump alpine version

* chore(builder-image-skaffold): bump all tools

The container-structure-test has a CVE due to a containerd dependency,
it will probably get resolved eventually.

* chore(builder-image-terraform): rotate hashicorp key & bump versions

New key copied from https://www.hashicorp.com/security#current-key

* chore(builder-image-terratest): rotate hashicorp key and bump versions

Key copied from https://www.hashicorp.com/security#current-key

* chore(jenkins-image): bump jenkins image

* chore(runner-image-lead-terraform): bump versions

* fix(tests): update tests to the correct versions

* fix(tests): fix goreleaser test

* chore(terraform): bump tf to patch 1.2.1
@chenrui333
Copy link
Member Author

I think we have waited long enough to unpin/close the issue.

@chenrui333 chenrui333 unpinned this issue Jul 7, 2022
@chenrui333
Copy link
Member Author

Feel free to submit a new one.

krrrr38 pushed a commit to krrrr38/atlantis that referenced this issue Dec 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants