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

Issue with connecting multiple provider container networks #264

Open
eemcmullan opened this issue Jun 20, 2024 · 2 comments
Open

Issue with connecting multiple provider container networks #264

eemcmullan opened this issue Jun 20, 2024 · 2 comments
Assignees
Labels
needs-kind Indicates an issue or PR lacks a `kind/foo` label and requires one. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Milestone

Comments

@eemcmullan
Copy link
Collaborator

Right now, to run multiple provider containers, we start the first provider container by network name, and then start the other providers by the name of the first provider container. This is probably unnecessary, and can be cleaned up in a way to start each provider with the network name.
However, after attempting this, only the first running provider container connected to the analyzer even though inspection of the network showed all provider containers connected.

@eemcmullan eemcmullan self-assigned this Jun 20, 2024
@konveyor-ci-bot konveyor-ci-bot bot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jun 20, 2024
@konveyor-ci-bot
Copy link

This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.
The triage/accepted label can be added by org members.

@konveyor-ci-bot konveyor-ci-bot bot added needs-kind Indicates an issue or PR lacks a `kind/foo` label and requires one. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. labels Jun 20, 2024
@eemcmullan
Copy link
Collaborator Author

Connecting the containers to the same network does work now, it's just done poorly. Bumping to 0.6

@eemcmullan eemcmullan added this to the v0.6.0 milestone Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-kind Indicates an issue or PR lacks a `kind/foo` label and requires one. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Status: 📋 Backlog
Development

No branches or pull requests

1 participant