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

[bug] Fixed the panic for uninitialized docker daemon #1958

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

Manik2708
Copy link

Purpose of PR?:

Fixes #1948

Does this PR introduce a breaking change? No

If the changes in this PR are manually verified, list down the scenarios covered::

Additional information for reviewer? :
cc @daemon1024 I am not able to reproduce the error, please can you verify whether this change is able to avoid panic or help me in reproducing this panic

Checklist:

  • Bug fix. Fixes #
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • PR Title follows the convention of <type>(<scope>): <subject>
  • Commit has unit tests
  • Commit has integration tests

@Manik2708
Copy link
Author

@daemon1024 Please see the description!

@@ -455,6 +456,7 @@ func (dm *KubeArmorDaemon) GetAlreadyDeployedDockerContainers() {
} else {
dm.Logger.Warnf("Error while listing containers: %s", err)
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do this need to terminate KubeArmorDaemon also?

@Manik2708
Copy link
Author

@rksharma95 @Aryan-sharma11 @daemon1024 Please review!

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

Successfully merging this pull request may close these issues.

KubeArmor Panic if uninitialised docker socket exists
1 participant