Skip to content

Conversation

alexeagle
Copy link
Collaborator

Previously we documented that users should use the container_test rule from rules_docker.

However, rules_docker is no longer maintained, and that rule was never documented.
rules_oci means to be a replacement, but doesn't want to add a container_test rule for a binary that is published elsewhere.

It's easier to understand if this repo publishes both the binary, and the bazel rule that wraps it, so that any changes can be made to them together.

@alexeagle alexeagle force-pushed the main branch 5 times, most recently from 9c1c7f3 to bce2c73 Compare April 24, 2023 22:05
@alexeagle alexeagle force-pushed the main branch 7 times, most recently from 7a79331 to 5bfcfef Compare April 29, 2023 17:49
@loosebazooka
Copy link
Member

loosebazooka commented May 2, 2023

bleh, this macos build with podman is being weird.
maybe the default DOCKER_HOST location moved with the newest podman?

@loosebazooka
Copy link
Member

kk think this just needs a rebase once #343 goes in.

alexeagle added 4 commits May 2, 2023 11:54
Previously we documented that users should use the container_test rule from rules_docker:
https://github.com/bazelbuild/rules_docker/blob/8c3a8110a0c519929a7e79c39ac345a0f8c74d04/contrib/test.bzl#L125
However, rules_docker is no longer maintained. rules_oci means to be a replacement, but doesn't want to add a rule for a binary that is published elsewhere.
It's easier to understand if this repo publishes both the binary, and the bazel rule that wraps it, so that any changes can be made to them together.
@alexeagle
Copy link
Collaborator Author

Rebased, thanks for fixing the CI setup

@loosebazooka loosebazooka merged commit 4549390 into GoogleContainerTools:main May 2, 2023
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

Successfully merging this pull request may close these issues.

4 participants