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

Bug 1840370: Configure "podman build" to produce images with Docker manifests. #337

Conversation

benluddy
Copy link
Contributor

Podman's default is to produce OCI manifests and metadata, while
Docker (unsurprisingly) produces the Docker filetypes. This can lead
to behavior differences down the line, especially once container
registries are added to the mix.

@benluddy
Copy link
Contributor Author

/test unit

@benluddy benluddy force-pushed the podman-index-docker-format branch from 5eb38ea to 9338ad9 Compare May 26, 2020 18:18
@benluddy
Copy link
Contributor Author

/test e2e-aws

@benluddy benluddy changed the title Configure "podman build" to produce images with Docker manifests. Bug 1840370: Configure "podman build" to produce images with Docker manifests. May 26, 2020
@openshift-ci-robot openshift-ci-robot added the bugzilla/severity-low Referenced Bugzilla bug's severity is low for the branch this PR is targeting. label May 26, 2020
@openshift-ci-robot
Copy link

@benluddy: This pull request references Bugzilla bug 1840370, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.5.0) matches configured target release for branch (4.5.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1840370: Configure "podman build" to produce images with Docker manifests.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label May 26, 2020
func (p *PodmanCommandFactory) BuildCommand(o BuildOptions) (*exec.Cmd, error) {
args := []string{"build"}

if o.format != "" {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dumb thought: do we ever want to consider just passing arbitrary command arguments here rather than being explicit with flags? It might make for a simpler cli experience. Especially if we make the default for build fully daemonless

The counter is that we're on the hook for making all of these arbitrary flags work? 🤷

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you could make a good argument for that, but I lean towards letting users directly invoke podman/whatever if they are in a circumstance that calls for it.

pkg/containertools/option_build.go Show resolved Hide resolved
pkg/containertools/factory_test.go Show resolved Hide resolved
Podman's default is to produce OCI manifests and metadata, while
Docker (unsurprisingly) produces the Docker filetypes. This can lead
to behavior differences down the line, especially once container
registries are added to the mix.
@benluddy benluddy force-pushed the podman-index-docker-format branch from 9338ad9 to a9d758c Compare May 27, 2020 15:35
@benluddy benluddy requested a review from kevinrizza May 27, 2020 17:07
@kevinrizza
Copy link
Member

/lgtm
/approve

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label May 27, 2020
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: benluddy, kevinrizza

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 27, 2020
@openshift-merge-robot openshift-merge-robot merged commit 7437af6 into operator-framework:master May 27, 2020
@openshift-ci-robot
Copy link

@benluddy: All pull requests linked via external trackers have merged: operator-framework/operator-registry#337. Bugzilla bug 1840370 has been moved to the MODIFIED state.

In response to this:

Bug 1840370: Configure "podman build" to produce images with Docker manifests.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-low Referenced Bugzilla bug's severity is low for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants