-
Notifications
You must be signed in to change notification settings - Fork 2.7k
The buildx inspect
command is missing
#13014
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
Comments
Ah! Thank you - I should have checked that first. I'm on the latest release but it looks like the command will be there soon. |
Although, I can't see anything in the release notes (or source) relating to |
https://github.com/vmware-tanzu/velero/blob/main/Makefile#L73-L77 For velero it is easy enough to workaround by running Other than this and containers/buildah#3799 it does work though. |
Is docker buildx inspect the same as docker image inspect or docker inspect? |
Could you append the output of docker buildx inspect? |
|
Sorry, I missed
|
|
We don't plan on doing this at this time, the question is could we implement parts of buildx, to make switching scripts from one tool to another easier. |
If you can't implement buildx inspect, which upstream projects are using to determine if the buildx plugin is installed and enabled in docker, do you have a recommendation on how such a check might be implemented so that it works universally? Otherwise between this and the issue related to not handling the output flag it gets more difficult using podman as a replacement in conjunction with projects where you don't control the source. |
We can implement a dummy output for I am closing this issue since it falls more into category of |
Reopening as a user asked to. |
Dummy outputs is acceptable imo as long as it’s documented in migration docs etc. This ack could be generated by Could be explicit ack in some config file manually as well. This should make any systems using inspect command to assume buildx is enabled and to proceed using other buildx commands like Any buildx subcommands not supported will explicitly be printed out as part of this ack command. |
There should be some non dummy data as part of this output, such as supported platforms that podman can output. |
I added support for "podman buildx inspect" It supports issue containers#13014. Since podman doesn't support Buildkit the version was ignored. For platforms both emulated and host platforms was included while the rest became normal prints meant to replicate what "docker buildx inspect" returned. I also added support for the "--bootstrap" flag that corresponds to the docker command. So far this is considered a NOP so it returns the same output as though it wasn't there. This file can be found in cmd/podman/images/buildx_inspect.go and test can be found at test/e2e/buildx_inspect_test.go Signed-off-by: Joshua Arrevillaga <[email protected]>
Added support for "podman buildx inspect". The goal was to replicate the default output from "docker buildx inspect" as much as possible but a problem encountered was podman not supporting BuildKit. To replicate the output I resorted to printing the statements with default values but only changed the driver name to use podman instead of docker. Since there was no buildkit, gave it the value of "N/A" to depict it's not supported. For Platforms, I resorted to using the emulated architectures found on your linux system + the host architecture of your local machine or podman server. The bootstrap flag was also added but is considered a NOP since there is no buildkit container to run before running inspect. An extra field was added to the HostInfo struct so when you run "podman info" the emulated architectures will show, this was used so you can grab the information from the podman engine. Fixes containers#13014 Signed-off-by: Joshua Arrevillaga <[email protected]>
Added support for "podman buildx inspect". The goal was to replicate the default output from "docker buildx inspect" as much as possible but a problem encountered was podman not supporting BuildKit. To replicate the output I resorted to printing the statements with default values but only changed the driver name to use podman instead of docker. Since there was no buildkit, gave it the value of "N/A" to depict it's not supported. For Platforms, I resorted to using the emulated architectures found on your linux system + the host architecture of your local machine or podman server. The bootstrap flag was also added but is considered a NOP since there is no buildkit container to run before running inspect. An extra field was added to the HostInfo struct so when you run "podman info" the emulated architectures will show, this was used so you can grab the information from the podman engine. Fixes containers#13014 Signed-off-by: Joshua Arrevillaga <[email protected]>
Added support for "podman buildx inspect". The goal was to replicate the default output from "docker buildx inspect" as much as possible but a problem encountered was podman not supporting BuildKit. To replicate the output I resorted to printing the statements with default values but only changed the driver name to use podman instead of docker. Since there was no buildkit, gave it the value of "N/A" to depict it's not supported. For Platforms, I resorted to using the emulated architectures found on your linux system + the host architecture of your local machine or podman server. The bootstrap flag was also added but is considered a NOP since there is no buildkit container to run before running inspect. An extra field was added to the HostInfo struct so when you run "podman info" the emulated architectures will show, this was used so you can grab the information from the podman engine. Fixes containers#13014 Signed-off-by: Joshua Arrevillaga <[email protected]>
Added support for "podman buildx inspect". The goal was to replicate the default output from "docker buildx inspect" as much as possible but a problem encountered was podman not supporting BuildKit. To replicate the output I resorted to printing the statements with default values but only changed the driver name to use podman instead of docker. Since there was no buildkit, gave it the value of "N/A" to depict it's not supported. For Platforms, I resorted to using the emulated architectures found on your linux system + the host architecture of your local machine or podman server. The bootstrap flag was also added but is considered a NOP since there is no buildkit container to run before running inspect. An extra field was added to the HostInfo struct so when you run "podman info" the emulated architectures will show, this was used so you can grab the information from the podman engine. Fixes containers#13014 Signed-off-by: Joshua Arrevillaga <[email protected]>
Added support for "podman buildx inspect". The goal was to replicate the default output from "docker buildx inspect" as much as possible but a problem encountered was podman not supporting BuildKit. To replicate the output I resorted to printing the statements with default values but only changed the driver name to use podman instead of docker. Since there was no buildkit, gave it the value of "N/A" to depict it's not supported. For Platforms, I resorted to using the emulated architectures found on your linux system + the host architecture of your local machine or podman server. The bootstrap flag was also added but is considered a NOP since there is no buildkit container to run before running inspect. An extra field was added to the HostInfo struct so when you run "podman info" the emulated architectures will show, this was used so you can grab the information from the podman engine. Fixes containers#13014 Signed-off-by: Joshua Arrevillaga <[email protected]>
Added support for "podman buildx inspect". The goal was to replicate the default output from "docker buildx inspect" as much as possible but a problem encountered was podman not supporting BuildKit. To replicate the output I resorted to printing the statements with default values but only changed the driver name to use podman instead of docker. Since there was no buildkit, gave it the value of "N/A" to depict it's not supported. For Platforms, I resorted to using the emulated architectures found on your linux system + the host architecture of your local machine or podman server. The bootstrap flag was also added but is considered a NOP since there is no buildkit container to run before running inspect. An extra field was added to the HostInfo struct so when you run "podman info" the emulated architectures will show, this was used so you can grab the information from the podman engine. Fixes containers#13014 Signed-off-by: Joshua Arrevillaga <[email protected]>
Added support for "podman buildx inspect". The goal was to replicate the default output from "docker buildx inspect" as much as possible but a problem encountered was podman not supporting BuildKit. To replicate the output I resorted to printing the statements with default values but only changed the driver name to use podman instead of docker. Since there was no buildkit, gave it the value of "N/A" to depict it's not supported. For Platforms, I resorted to using the emulated architectures found on your linux system + the host architecture of your local machine or podman server. The bootstrap flag was also added but is considered a NOP since there is no buildkit container to run before running inspect. An extra field was added to the HostInfo struct so when you run "podman info" the emulated architectures will show, this was used so you can grab the information from the podman engine. Fixes containers#13014 Signed-off-by: Joshua Arrevillaga <[email protected]>
Added support for "podman buildx inspect". The goal was to replicate the default output from "docker buildx inspect" as much as possible but a problem encountered was podman not supporting BuildKit. To replicate the output I resorted to printing the statements with default values but only changed the driver name to use podman instead of docker. Since there was no buildkit, gave it the value of "N/A" to depict it's not supported. For Platforms, I resorted to using the emulated architectures found on your linux system + the host architecture of your local machine or podman server. The bootstrap flag was also added but is considered a NOP since there is no buildkit container to run before running inspect. An extra field was added to the HostInfo struct so when you run "podman info" the emulated architectures will show, this was used so you can grab the information from the podman engine. Fixes containers#13014 Signed-off-by: Joshua Arrevillaga <[email protected]>
/kind feature
Description
I am looking into whether it is possible to use Podman as a replacement for Docker with Python on Whales, a Python wrapper for the Docker CLI.
Things look great so far, however, one issue I discovered is that Podman doesn't implement the
buildx inspect
sub-command. The output of this command is parsed bypython_on_whales
and the required fields in the the output areName
andDriver
(see https://github.com/gabrieldemarmiesse/python-on-whales/blob/4d5b8b4c5c6dc3ac0af5713e4fe5a72788f44cda/python_on_whales/components/buildx/models.py#L12)Steps to reproduce the issue:
podman buildx inspect
Describe the results you received:
Describe the results you expected:
This is the equivalent output from
docker
:Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):The text was updated successfully, but these errors were encountered: