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

Simple differences between podman inspect and docker inspect of container images. #305

Closed
rhatdan opened this issue Feb 7, 2018 · 4 comments
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@rhatdan
Copy link
Member

rhatdan commented Feb 7, 2018

Comparing inspect between

docker pull registry.fedoraproject.org/f26/httpd:latest
podman pull registry.fedoraproject.org/f26/httpd:latest

docker inspect registry.fedoraproject.org/f26/httpd:latest

podman inspect registry.fedoraproject.org/f26/httpd:latest

Quickly what I see.

Podman refers to "ID", while Docker refers to "Id", can we change this? or is this buried in container storage. Also Docker id has a sha256: prepended on it, while Podman does not?

The Config Section on Podman is referred to as ContainerConfig on Docker, I think this should change.

Docker shows a "hostname:" field equivalent to the shortname of the image, while podman does not show this field at all? Not sure this matters, since I don't know what a hostname for a container image means anyways.

Command field in podman is

    "Cmd": [
        "/usr/bin/run-httpd"
    ],

Docker:

        "Cmd": [
            "/bin/sh",
            "-c",
            "#(nop) USER [1001]"
        ],

Docker has an entrypoint field, while podman does not, Entrypoint=null?

@mheon
Copy link
Member

mheon commented Feb 21, 2018

@rhatdan Can we close this? I think #306 fixed it

@rhatdan
Copy link
Member Author

rhatdan commented Feb 21, 2018

I will close this but we still have the issue where docker inspect accepts multiple containers and returns a list. Where podman only takes one. @baude is working on this I believe.

@mheon
Copy link
Member

mheon commented Feb 21, 2018

I think that merged as well?

@mheon
Copy link
Member

mheon commented Feb 21, 2018

It did, 6ce70a3

@mheon mheon closed this as completed Feb 21, 2018
@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 Sep 24, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

No branches or pull requests

2 participants