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
Is your enhancement related to a problem? Please describe
If there is an issue with the build process BEFORE we start the container, we should link this into the image log file.
The reasoning is that users who experience issues we have to ask them to look at their console logs which may not be very accessible / issues getting them (have to go to troubleshooting then logs tab).
Instead, we should output any errors encountered during the build process into the image log file as well.
I encountered this a lot during implementing #623 where having log output related to issues with the API would of been handy during the build process.
Describe the solution you'd like
For example:
Press build button / build form
Issue starting container related to Podman Desktop
Output log to image log file (it was already created before hand).
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
### What does this PR do?
Adds some simple code that also outputs any errors with the function to
the log file for debugging purposes / being able to help for any
debugging.
### Screenshot / video of UI
<!-- If this PR is changing UI, please include
screenshots or screencasts showing the difference -->
N/A
### What issues does this PR fix or reference?
<!-- Include any related issues from Podman Desktop
repository (or from another issue tracker). -->
Closescontainers#678
### How to test this PR?
<!-- Please explain steps to reproduce -->
1. Before pressing build, stop your Podman Machine
2. See that it outputs the connection error into the build log file.
Signed-off-by: Charlie Drage <[email protected]>
Is your enhancement related to a problem? Please describe
If there is an issue with the build process BEFORE we start the container, we should link this into the image log file.
The reasoning is that users who experience issues we have to ask them to look at their console logs which may not be very accessible / issues getting them (have to go to troubleshooting then logs tab).
Instead, we should output any errors encountered during the build process into the image log file as well.
I encountered this a lot during implementing #623 where having log output related to issues with the API would of been handy during the build process.
Describe the solution you'd like
For example:
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: