fix: check config file before accessing values #1120
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available: N/A
Description of changes:
Adding null pointer checks for finch config file prior to attempting to access the
fc.dockercompat
configuration option.According to
main_native.go:45-46
, in the specific scenario that thefinch.yaml
config fails to load due toos.ErrPermission
, then a null pointer is passed to the application when initializing NerdctlCommands.The recently introduced dependence upon the
fc.DockerCompat
configuration option resulted in a segmentation violation of nil pointer dereference for Finch on Linux use-case.Testing done:
Manual debugger testing
I've reviewed the guidance in CONTRIBUTING.md
License Acceptance
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.