You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to be able to generate a config.json based on the output of docker inspect or podman inspect. Images (or containers) already have knowledge of things like exposed ports, commands to run, etc. and it'd be nice to be able to use that as a base for generating a config.json.
Example:
oci-runtime-tool generate --image image.json …
The text was updated successfully, but these errors were encountered:
I this it's a good idea, and I'm prepared to do this.
As you said, before running this function we need a json file of the results of the docker inspect, and then we run the generate function on this basis to produce the new json file. Is my understanding correct?
Yes. I suspect there are multiple different formats out there (Docker-specific, OCIv1, probably others from other tools), but I think they all have a MIME type key in there somewhere to tell them apart from each other.
It would be nice to be able to generate a
config.json
based on the output ofdocker inspect
orpodman inspect
. Images (or containers) already have knowledge of things like exposed ports, commands to run, etc. and it'd be nice to be able to use that as a base for generating aconfig.json
.Example:
The text was updated successfully, but these errors were encountered: