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

show verbose debug log #5612

Open
FBIanderson opened this issue Dec 23, 2024 · 1 comment
Open

show verbose debug log #5612

FBIanderson opened this issue Dec 23, 2024 · 1 comment

Comments

@FBIanderson
Copy link

When I run this type of Dockerfile

FROM debian
RUN ls -al  / 

I want to know the details of root path of the image, but it will show nothing, is there any option like -v(verbose) to show the full log

@thaJeztah
Copy link
Member

Can you provide more information about the problem you're trying to solve, and what you need this information for?

Some (most) of these paths should be considered internal information used by docker and BuildKit, and are not intended to be accessed other than through BuildKit (or docker) itself. Depending on how you're running the build, these paths may also be inside a container or volume (when using a BuildKit instance using a container driver), or may be ephemeral locations only present during the build.

For example, the RUN step may create a new writable mount that's only present for the duration of the RUN step, but no longer afterwards.

Having more insight in the problem you're trying to solve may be useful here to see if there's anything to address / improve.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants