-
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
podman build with remote is always silent (logging level does not work) #7498
Labels
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
It doesn't seem to be "just" the logging, I don't actually get any image built either... podman1-remote build .
STEP 1: FROM busybox
Getting image source signatures
Copying blob sha256:61c5ed1cbdf8e801f3b73d906c61261ad916b2532d6756e7c4fbcacb975299fb
Copying config sha256:018c9d7b792b4be80095d957533667279843acf9a46c973067c8d1dff31ea8b4
Writing manifest to image destination
Storing signatures
STEP 2: RUN true
STEP 3: COMMIT
--> 7e7fa3f44ea
7e7fa3f44eac8d87b87fb232c3b40a07b08f1661ef8bd86e4debd3a59086280a
podman1-remote images
REPOSITORY TAG IMAGE ID CREATED SIZE
<none> <none> 7e7fa3f44eac About a minute ago 1.45 MB
docker.io/library/busybox latest 018c9d7b792b 4 weeks ago 1.45 MB
podman2-remote build .
podman2-remote images
REPOSITORY TAG IMAGE ID CREATED SIZE
docker.io/library/busybox latest 018c9d7b792b 4 weeks ago 1.45 MB
The base image is there, because I ran a simple "run" test before the "build". |
edsantiago
changed the title
podmain buid with remote is always silent (logging level does not work)
podman build with remote is always silent (logging level does not work)
Sep 2, 2020
closed via #7452 |
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 22, 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.
Description
podman build seems totally silent. when run locally this does not happen.
Apparently the entire stdout/stderr is lost.
Steps to reproduce the issue:
Describe the results you received:
no stdout/stderr whatsover/
Describe the results you expected:
Some stderr logging information, especially when using
--loglevel 1,2,3
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: