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

'podman commit -f docker -m' WARN:COMMENT is not supported for OCI image format #17773

Closed
xiayushidai opened this issue Mar 14, 2023 · 1 comment · Fixed by #18212
Closed
Labels
Good First Issue This issue would be a good issue for a first time contributor to undertake. kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@xiayushidai
Copy link

Issue Description

I use 'podman commit -f docker -m "xxx"' to create a image, but report a WARN: COMMENT is not supported for OCI image format, comment xxx will be ignored. Must use 'docker' format. Alreaday specifiend -f docker, why is there still this warning

Steps to reproduce the issue

Steps to reproduce the issue

  1. podman pull busybox
  2. podman run --name test_commit -itd busybox sleep 1d
  3. podman commit -f docker -m "test" test_commit test_image

Describe the results you received

WARN: COMMENT is not supported for OCI image format, comment xxx will be ignored. Must use 'docker' format

Describe the results you expected

No warning

podman info output

4.4.2 in fedora37. everything is default.

Podman in a container

No

Privileged Or Rootless

None

Upstream Latest Release

Yes

Additional environment details

Additional environment details

Additional information

Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting

@xiayushidai xiayushidai added the kind/bug Categorizes issue or PR as related to a bug. label Mar 14, 2023
@github-actions
Copy link

A friendly reminder that this issue had no activity for 30 days.

@rhatdan rhatdan added Good First Issue This issue would be a good issue for a first time contributor to undertake. and removed stale-issue labels Apr 14, 2023
rhatdan added a commit to rhatdan/podman that referenced this issue Apr 15, 2023
If user specifies commit --format, we were not setting it before
commit, this caused warning messages that made no sense to be
printed that made no sense.

Fixes: containers#17773

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
rhatdan added a commit to rhatdan/podman that referenced this issue Apr 20, 2023
If user specifies commit --format, we were not setting it before
commit, this caused warning messages that made no sense to be
printed that made no sense.

Fixes: containers#17773

Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Aug 26, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Good First Issue This issue would be a good issue for a first time contributor to undertake. kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants