Hi All,
I’m facing a situation while setting up the Alta Controller in Docker that I would like some help with. Here’s the challenge:
- The Alta Controller needs to run on a specific IP address, which requires the router to be set up first.
- However, I need the router to be configured after the controller is running, creating a Catch-22 scenario.
Has anyone run into this issue or found a better approach to simultaneously configure the Alta Controller and the router?
Any insights would be much appreciated!
There is nothing holding you back from defining the network for the Control directly inside the container, such as in /etc/network/interfaces. I believe you could start with that, or otherwise define the network using docker.
thank you. also is there a way for me to be self sufficient with the controller (and not depend on Alta.inc login etc - I mean no external dependencies.
The account you create in your self-hosted controller will not be shared with the cloud in any capacity.
When I start the controller for the first time, I need to activate it, and each time I reinstall it, I have to activate it again, which requires an activation email from manage.alta.inc. Also, the login credentials for the Docker image are stored on Alta’s servers and validated through them, I thought, thanks for confirming it is not the case.
Could you please clarify if there are any external dependencies, or if it’s possible to be completely self-sufficient without relying on Alta’s servers?
The validation of your license must be processed by our services in the cloud. This is unfortunately unavoidable.
Thank you for quick help. really appreciate it.