Open ronsrebro opened 3 months ago
Not sure this is the official way. I did the below.
-docker run -it -p 3000:3000 flowiseai/flowise:latest sh -npx flowise start
Can you also try changing the EOL of following 2 files to LF
:
packages/server/bin/dev
packages/server/bin/run
Same here: just added this CMD
Describe the bug Following the instruction in https://docs.flowiseai.com/getting-started for Docker Image installation. When the container is run, it exists after 2 seconds with this log:
2024-03-29 09:52:16 Flowiseai Server 2024-03-29 09:52:16 2024-03-29 09:52:16 VERSION 2024-03-29 09:52:16 flowise/1.6.2 linux-arm64 node-v18.20.0 2024-03-29 09:52:16 2024-03-29 09:52:16 USAGE 2024-03-29 09:52:16 $ flowise [COMMAND] 2024-03-29 09:52:16 2024-03-29 09:52:16 COMMANDS 2024-03-29 09:52:16 start
To Reproduce Follow the instruction in https://docs.flowiseai.com/getting-started for Docker Image installation:
Build the image locally: docker build --no-cache -t flowise . Run image: docker run -d --name flowise -p 3000:3000 flowise
See container logs
Expected behavior Docker container running at flowise available at 127.0.0.1
Screenshots