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

Create a all-in-one container for user to easier access/play with nebula #2791

Closed
wey-gu opened this issue Sep 5, 2021 · 2 comments
Closed
Assignees
Labels
type/feature req Type: feature request

Comments

@wey-gu
Copy link
Contributor

wey-gu commented Sep 5, 2021

As titled, and we had that in 1.x if I recall it correctly :)

One case that makes this necessary is in ARM/M1 Mac the Docker Desktop is not in good enough shape to enable multi-container communication in case it's running x64 container, thus nebula-docker-compose won't work properly.

Thanks.

@yixinglu
Copy link
Contributor

I don't want to provide users with such an all in one container. I prefer to build an arm-arch docker image for nebula to solve user problems. Later we can provide an all in one docker compose orchestration file, which can contain our nebula service, studio service or explore service and so on. This makes more sense for users to start all nebula services in one command.

@wey-gu
Copy link
Contributor Author

wey-gu commented Sep 16, 2021

I don't want to provide users with such an all in one container. I prefer to build an arm-arch docker image for nebula to solve user problems. Later we can provide an all in one docker compose orchestration file, which can contain our nebula service, studio service or explore service and so on. This makes more sense for users to start all nebula services in one command.

Agreed, even better! That'll be awesome to have one compose file with both core and graphic interface services/observation services with arch64 support!

@Sophie-Xie Sophie-Xie removed this from the v2.6.0 milestone Sep 17, 2021
yixinglu pushed a commit to yixinglu/nebula that referenced this issue Sep 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feature req Type: feature request
Projects
None yet
Development

No branches or pull requests

4 participants