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

how to deploy Nanocl using the bare process method? #1035

Open
NicholasLiuWei opened this issue Aug 22, 2024 · 3 comments
Open

how to deploy Nanocl using the bare process method? #1035

NicholasLiuWei opened this issue Aug 22, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@NicholasLiuWei
Copy link

I want to deploy nanocl locally using a binary method and then debug it. Could you provide a script similar to the hack/local-up-cluster.sh script in Kubernetes?”

@NicholasLiuWei NicholasLiuWei added the enhancement New feature or request label Aug 22, 2024
@leon3s
Copy link
Member

leon3s commented Aug 22, 2024

Hey, i'm not totally sure i understand what you wanna do, what you wanna debug ?

To install nanocl locally for development purpose you can use the nanocl install command.
Then build an image using docker build and use it directly in nanocl.

There is an example on how you can use it for local development there:
https://github.com/leon3s/solving-localhost-dev

@NicholasLiuWei
Copy link
Author

can the components, including nanocld, ncdns, ndns, ncproxy, nproxy, metrsd, and cockroach, that currently run in containers, be run directly on the operating system?

@leon3s
Copy link
Member

leon3s commented Aug 22, 2024

Where it's technically possible, it's not really designed this way, it's way more easier to have them as container for security and update, you can patch the components without causing downtime.
Using a Statefile or the patch command, you can also manage their life cycle with nanocl commands.

For debugging purpose you should be able to attach GDB using the process ID.

To run outside a container, the components would require (for some of them) root access, it would also require to write systemd scripts to restart them in case of failure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants