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

Fatal error in container-management service #252

Open
MohamedAbdulslam opened this issue Jan 23, 2025 · 0 comments
Open

Fatal error in container-management service #252

MohamedAbdulslam opened this issue Jan 23, 2025 · 0 comments

Comments

@MohamedAbdulslam
Copy link

I am encountring an run time error while dialing container-management.socket. The function that returns that erroe is in the containerm component in this repo. I am just cloning the kanto repo that contain a recipe container-management_git.bb that use this repo, so I don't know if it is configuration isssue or what.
Error: panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x58 pc=0xf30fc0]
The error occurs in the initializeDefaultHostNetwork function, which is part of the network initialization process for the container management service. The panic message indicates that the code is trying to access a memory address that is nil (not initialized).
Any help will be appreciated.

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

1 participant