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.

Sign up for GitHub

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

Jump to bottom

Issue when multiple containerd sockets exists #1133

Closed
aviramha opened this issue Feb 28, 2023 · 0 comments · Fixed by #1134
Closed

Issue when multiple containerd sockets exists #1133

aviramha opened this issue Feb 28, 2023 · 0 comments · Fixed by #1134
Assignees
@aviramha
Labels
bug Something isn't working

Comments

@aviramha
Copy link
Member

Bug Description

Source: https://discord.com/channels/933706914808889356/1080038847812997180
tl;dr - user node has 2 containerd sockets, and mirrord agent connects to the first one it finds, in the user's case that was the wrong containerd socket.

Steps to Reproduce

install k3s and containerd separately

Backtrace

No response

Relevant Logs

No response

Your operating system and version

n/a

Local process

n/a

Local process version

No response

Additional Info

No response
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aviramha aviramha

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

handle cases in agent where 2+ containerd sockets exist aviramha/mirrord
1 participant
@aviramha