-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Os is empty string #5503
Comments
im looking into this ... i have determined that podman build is not setting the field. it is not inspect which was my first concern. |
when building images, we can now add the os and arch of the image using overrides from the commandline. the commandline options set sane defaults so we use those as well. Fixes: containers#5503 Signed-off-by: Brent Baude <[email protected]>
@vertti if you can try the PR and report back, that is always helpful. |
Thanks, I will take the fix for a spin! But why isn't everyone using OpenShift stumbled to this issue? What are they using to get their custom containers to run on OpenShift? I must be missing something here.. |
This seems to be have introduced with a more aggressive check for os in added on 22nd Nov 2019. The check stopped raising an error on 31st Jan 2020. Perhaps OpenShift is using code from this window? |
when building images, we can now add the os and arch of the image using overrides from the commandline. the commandline options set sane defaults so we use those as well. Fixes: containers#5503 Signed-off-by: Brent Baude <[email protected]>
/kind bug
Description
Originally filed it to buildah here containers/buildah#2225 but it seems not to be a buildah issue.
Steps to reproduce the issue:
podman build
produces images that when inspected showOs
field as empty""
instead of expectedlinux
.OpenShift refuses to run these containers and prints out:
Steps to reproduce the issue:
Dockerfile
like:podman build -t website .
podman inspect website
Describe the results you received:
Check
Os
field in the output. It's""
instead of"linux"
Describe the results you expected:
Check
Os
field in the output. It's""
instead of"linux"
Running for example
podman inspect node:12-buster
will show"Os": "linux",
Additional information you deem important (e.g. issue happens only occasionally):
While discussing on the
buildah
issue tracker, it seems buildah will get the correctOs
field:I also get the correct
"linux"
result with yourbuildah
command. Butpodman
still prints empty string forOs
.but continuing with
podman
you can see the layer hashes match:and the
Os
is still emptyOutput of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Additional environment details (AWS, VirtualBox, physical, etc.):
Running podman with sudo on ubuntu 19.10
The text was updated successfully, but these errors were encountered: