Skip to content

Conversation

@Infra-Red
Copy link
Contributor

What is this change about?

The registry-image resource was introduced more than two years ago as a drop-in replace for the docker-image resource. It's less resource-intense, faster, and doesn't rely on spawning a Docker daemon.

Please provide contextual information.

Please check all that apply for this PR:

  • introduces a new task
  • changes an existing task
  • changes the Dockerfile
  • introduces a breaking change (other users will need to make manual changes when this is released)

Did you update the README as appropriate for this change?

  • YES
  • N/A

How should this change be described in release notes?

Replace docker-image with registry-image resource.

What is the level of urgency for publishing this change?

  • Urgent - unblocks current or future work
  • Slightly Less than Urgent

Tag your pair, your PM, and/or team!

N/A.

The registry-image resource was introduced more than two years
ago as a drop-in replace for the docker-image resource. It's
less resource-intense, faster, and doesn't rely on spawning a
Docker daemon.

See https://github.com/concourse/registry-image-resource for more
details.

Signed-off-by: Andrei Krasnitski <a.krasnitski@outlook.com>
@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/177429250

The labels on this github issue will be updated when the story is started.

@heycait heycait merged commit 8ab169d into cloudfoundry:main Mar 25, 2021
@heycait
Copy link

heycait commented Mar 25, 2021

Thanks for the PR!

@Infra-Red Infra-Red deleted the use-registry-image-resource branch March 25, 2021 21:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants