Once this command is executed (and a couple seconds given to Orion to boot) then I am able to access the UI at <VM_ip_address>:4200 from my computer.
While I can access the UI, I still have an error message Can't connect to Orion API at http://0.0.0.0:4200/api. Check that it's accessible from your machine.
Additionally, whatever deployment or run might be executed on the container, nothing is appearing on the interface. (This should be caused by the inaccessibility of the Orion API, if I understood the architecture correctly)
In this situation, how can I parameterize my Prefect container and/or Orion API to allow for the architecture needed?
Thanks a lot
I’ve just tried this method and there were no improvements to the situation. I still have the same error message.
Additionally, after running the orion, minio and agent profiles, I can’t seem to run any python code as demonstrated in the README (with the CLI). Whatever the code is, I get a HTTP Error 503: Service Unavailable with regards to http://orion:4200/api/health.
I have no idea how to solve this issue.
I am on Debian 11 (Bullseye), but the VM on which I intend to run Prefect is on AlmaLinux 8.7 (Stone Smilodon).
I followed the github README.md and I don’t find any one liner here?
When it comes to the step-by-step, the Orion API and UI have been deployed without errors, but accessing the address <VM's ip>:4200 from another machine, while displaying the interface, also returns the Can't connect to Orion API error. Additionally, the interface doesn’t seem functional for there are things missing (nothing in the Blocks tab, etc.)
The agent deployment happens without issue.
Executing the python flow.py command in the CLI yields the HTTP Error 503: Service Unavailable.
The goal here was to deploy a Prefect environment in a container (in the same fashion as Airflow can be). This is in order to compare the usage of Airflow and Prefect to maybe switch to Prefect as a solution.
Using this command, and connecting to the UI, I get a Can't connect to Orion API at http://127.0.0.1:4200/api. Check that it's accessible from your machine error.
The container is located on a remote virtual machine, and I canno’t seem to understand how the services are supposed to be organized/where they are located with this command.