Kestra Quickstart Guide – Run Your First Workflow
Launch Kestra locally, create a simple flow, and run your first execution in a few minutes.
Run your first Kestra Workflow with Docker
Start Kestra
Prerequisite: Make sure Docker is installed in your environment. We recommend Docker Desktop.
Once Docker is running, start Kestra with a single command. If you are using Windows, make sure to use WSL:
docker run --pull=always -it -p 8080:8080 --user=root \ --name kestra --restart=always \ -v kestra_data:/app/storage \ -v /var/run/docker.sock:/var/run/docker.sock \ -v /tmp:/tmp \ kestra/kestra:latest server localIf you re-run the command and Docker reports You have to remove (or rename) that container to be able to reuse that name., remove the old container with docker rm -f kestra or pick a different --name.
This command does the following:
- starts Kestra on port
8080 - stores local files in the
kestra_dataDocker volume - mounts
/tmpand the Docker socket so script and container tasks can run locally
Open http://localhost:8080 in your browser to launch the UI, create your user, and take the product tour to begin building your first flow.
The above command starts Kestra with an embedded H2 database that does not persist data. Storage files are stored on the kestra_data Docker volume. For production-ready persistence with a PostgreSQL database and more configurability, follow the Docker Compose installation.
Next steps
Congrats! You’ve taken the product tour, executed your first flow, and familiarized yourself with Kestra. Next, you can follow the documentation in this order to build on what you’ve learned so far:
- Continue with a Tutorial to add inputs, outputs, triggers, and more task types.
- Follow the full Installation guide for persistent local or distributed setups.
- Explore the available Plugins to integrate with external systems, and begin orchestrating your applications, microservices, and processes.
- Contribute to Kestra – whether a developer or not, we value outside contribution of all kinds: Plugins, Features, Documentation, Feature Requests, and Bug Reports. Get involved!
Was this page helpful?