Launch server + UI without Docker about server HOT 13 CLOSED

Good idea. I´m struggling too. A few months ago, I could manage to install Prefect on a clean VM. Now I have tried it already two times, always with the same error message after the command "prefect server start":
ERROR: Couldn't connect to Docker daemon at http+docker://localhost - is it running?
and
subprocess.CalledProcessError: Command '['docker-compose', 'pull']' returned non-zero exit status 1.

No idea what´s wrong. This is already nerve wrecking.

from server.

Hi all - yesterday was a holiday for the Prefect team (Labor Day in the US) so we're tackling your issue today.

We're working on some documentation for spinning up the various services in Server independent of the prefect server start command, which I believe will address @gatesn's issue; we'll update this ticket when that documentation is ready.

@GZangl and @JonathanLoscalzo - I'd encourage you to join our Community Slack channel for some help triaging your specific issues (@GZangl I think you've already done this) as it looks like they're probably not related to the original post.

from server.

I'm trying to install and run, and the same issue:

ERROR: 
        Can't find a suitable configuration file in this directory or any
        parent. Are you in the right directory?

        Supported filenames: docker-compose.yml, docker-compose.yaml
............
............
subprocess.CalledProcessError: Command '['docker-compose', 'down']' returned non-zero exit status 1.

Operating System: Ubuntu 18.04.5 LTS
Kernel: Linux 5.4.0-42-generic
Architecture: x86-64
Using pyenv with python 3.7.9

from server.

@JonathanLoscalzo
make sure, you don't have any error messages during installation. I had to install psutil manually, which required GCC to be installed:
sudo apt install build-essential
sudo apt-get install manpages-dev
pip3 install psutil

then I had to install python3-dev:

sudo apt install python3-dev

this allowed me to install prefect without errors. Now, when I start the server, I get this:
(prefect-env) georg@ubuntu:~$ prefect server start
Traceback (most recent call last):
File "urllib3/connectionpool.py", line 677, in urlopen
File "urllib3/connectionpool.py", line 392, in _make_request
File "http/client.py", line 1252, in request
File "http/client.py", line 1298, in _send_request
File "http/client.py", line 1247, in endheaders
File "http/client.py", line 1026, in _send_output
File "http/client.py", line 966, in send
File "docker/transport/unixconn.py", line 43, in connect
PermissionError: [Errno 13] Permission denied

but I'm one step further ;)
Good luck!

from server.

Moved this issue to the server repository, as it has more to do with prefect server than prefect core.

from server.

@jcrist - thanks a lot.
In the meantime, I have figured out how to get rid of the permission error:
I am running the server with following command from the bin folder: "sudo python3 prefect server start"

from server.

@znicholasbrown ,yes Nicholas, I moved to Slack and sorry for hijacking this issue. But it is related, as my problems started with the same error message as @JonathanLoscalzo had and I also share the confusion about the usage of docker and docker-composer.
The installation turns out to be very smooth, if all requirements are met and you work your way around the Linux permissions. So, my conclusion is: people have to be very carefully reading the error messages during installation and try to install the erroneous wheels manually (in my case psutil). This is a bit of a stretch for people like me, who lack proper understanding ;)

from server.

Hi all - yesterday was a holiday for the Prefect team (Labor Day in the US) so we're tackling your issue today.

We're working on some documentation for spinning up the various services in Server independent of the prefect server start command, which I believe will address @gatesn's issue; we'll update this ticket when that documentation is ready.

@GZangl and @JonathanLoscalzo - I'd encourage you to join our Community Slack channel for some help triaging your specific issues (@GZangl I think you've already done this) as it looks like they're probably not related to the original post.

You are right, I apologise for misunderstanding. I will go to slack.

And @GZangl also thanks!

from server.

We're working on some documentation for spinning up the various services in Server independent of the prefect server start command, which I believe will address @gatesn's issue; we'll update this ticket when that documentation is ready.

Hi @znicholasbrown , any update on this particular bit of documentation/news? Our clients require us to deploy our software on premises, mostly on windows server VMs, which unfortunately often times are unable to enable hyper-v/WSL (and therefore docker).

from server.

Hi @ReinierKop - this was something we ended up abandoning due to maintenance costs; one of the reasons we chose to use containers for the various services is exactly what you've described with Windows Server VMs - we don't have the ability to maintain all of the services in the Prefect stack in all of the environments such a feature would suggest. Using containerization allows us to maintain a single environment and its dependencies and focus instead on building features.

Apologies for not closing this issue earlier!

from server.

Alright, too bad :) Thanks for answering!

from server.

That said, the services are all run in-process for development in https://github.com/PrefectHQ/server/blob/master/src/prefect_server/cli/dev.py and if you can run the infrastructure apollo / hasura / postgres yourself outside of containers you should be able to accomplish this.

from server.

Yup, will try this definitely! We're already very happy Prefect Core works on windows without containers so this would simply be the cherry :). Thanks again!

from server.