Embucket can be installed using multiple methods depending on your environment and requirements. Choose the method that best fits your needs.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/embucket/embucket/llms.txt
Use this file to discover all available pages before exploring further.
System Requirements
Before installing Embucket, ensure your system meets these requirements:Operating System
- Linux (x86_64, ARM64)
- macOS (Intel, Apple Silicon)
- Windows (via WSL2)
Resources
- Minimum: 512MB RAM, 1 CPU core
- Recommended: 2GB+ RAM, 2+ CPU cores
Embucket is a single binary with zero external dependencies, making it easy to deploy in resource-constrained environments.
Installation Methods
Docker (Recommended)
The fastest way to get started with Embucket is using Docker.Docker with Custom Configuration
To use a custom configuration file with Docker:- Mounts your local
configdirectory to/app/configin the container - Passes the
--metastore-configflag to specify the configuration file
Pre-built Binary
Download pre-built binaries for your platform from the GitHub Releases page.Binary with Configuration
To run with a custom configuration file:The binary includes an embedded metastore for quick starts. For production deployments, use external catalog configuration.
Build from Source
For development or customization, build Embucket from source.Install prerequisites
Ensure you have the following installed:
- Rust toolchain (1.70 or later): Install from rustup.rs
- CMake: Required for some dependencies
- pkg-config: Required on Linux
- OpenSSL development libraries: Required on Linux
Build the project
Build in debug mode (faster compile, slower runtime):Or build in release mode (optimized for performance):
Release builds take longer to compile but run significantly faster. Use release mode for production deployments.
Build Options
Embucket supports optional features during compilation:Installation Verification
After installing Embucket using any method, verify the installation:Test the HTTP endpoint
Verify the server responds to HTTP requests:
If the health endpoint is not available, the server is running if you see log output without errors.
Connect with Snowflake CLI
Install and configure the Snowflake CLI to verify connectivity:See the Quickstart guide for detailed CLI setup instructions.
Environment Variables
Embucket can be configured using environment variables:| Variable | Description | Default |
|---|---|---|
METASTORE_CONFIG | Path to metastore configuration file | - |
JWT_SECRET | Secret key for JWT token generation | 63f4945d921d599f27ae4fdf5bada3f1 |
TRACING_LEVEL | Logging level (trace, debug, info, warn, error) | info |
RUST_LOG | Rust logging configuration | info |
OBJECT_STORE_BACKEND | Object storage backend (file, s3, gcs, azure) | file |
FILE_STORAGE_PATH | Local file storage path | data/ |
BUCKET_HOST | Host address to bind to | 0.0.0.0 |
Using Environment Variables
Troubleshooting
Docker Issues
Problem: Cannot connect to the Docker daemonProblem: Port 3000 is already in use
localhost:8080 instead.
Build Issues
Problem: Cargo build fails with linker errorsProblem: Out of memory during compilation
Runtime Issues
Problem: Permission denied when running the binaryProblem: Server starts but cannot connect from Snowflake CLI Solution: Check that:
-
The server is listening on the correct host:
- Firewall allows connections to port 3000
-
Snowflake CLI configuration uses
http://protocol (nothttps://)
Next Steps
Now that you have Embucket installed, continue with:Quickstart
Run your first queries in under 5 minutes
Configuration
Configure external catalogs and data sources
Deployment
Deploy Embucket to production environments
SQL Reference
Learn about Snowflake SQL support