Skip to content
This repository has been archived by the owner on Dec 17, 2024. It is now read-only.

Use network mechanics instead of links to expose containers to each other #257

Closed
lanwen opened this issue Jan 5, 2020 · 2 comments
Closed

Use network mechanics instead of links to expose containers to each other #257

lanwen opened this issue Jan 5, 2020 · 2 comments
Labels
new-feature
Milestone
1.7.2

Comments

@lanwen
Copy link
Contributor

lanwen commented Jan 5, 2020

Right now we are using links, which could lead to something like aerokube/selenoid-ui#277

Better to create a shared dedicated network, or by default discover one that is created for one of the containers
@lanwen lanwen mentioned this issue Jan 5, 2020
Closed
@patsevanton
Copy link

How create a shared dedicated network when run command cm ?

@vania-pooh
Copy link
Member

vania-pooh commented Jan 24, 2020 •
edited
Loading

@patsevanton currently there is no such feature but my idea is to use some easily defined network name (e.g. selenoid or selenoid-<hostname>) and then create such network if missing.

@vania-pooh vania-pooh added this to the 1.7.2 milestone Jan 27, 2020
aandryashin added a commit that referenced this issue Mar 1, 2020
@aandryashin
Merge pull request #260 from vania-pooh/master
0e66d86 
Starting everything on custom Docker network (fixes #257)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
new-feature
Projects
None yet
Milestone
1.7.2
Development

No branches or pull requests
3 participants
@vania-pooh @lanwen @patsevanton