immudb is not just a database; it’s a fortress for your sensitive data. By employing cryptographic proof and seamlessly tracking changes, immudb allows you to safeguard your information without trusting the database itself. In this article, let’s walk through how to get immudb operational, discuss its features, and troubleshoot any potential hiccups along the way.
Contents
Quickstart
Whether you’re using an executable, Docker, or Kubernetes, we’ll guide you on how to get immudb running.
Getting immudb Running: Executable
First, you will want to download the immudb binary from the latest releases on GitHub. Here’s how you can do it:
bash
wget https://github.com/codenotary/immudb/releases/download/v1.9.5/immudb-v1.9.5-linux-amd64
mv immudb-v1.9.5-linux-amd64 immudb
chmod +x immudb
# run immudb in the foreground to see all output.
./immudb
# or run immudb in the background.
./immudb -d
Getting immudb Running: Docker
You can quickly spin up immudb in a Docker container:
bash
docker run -d --net host -it --rm --name immudb codenotary/immudb:latest
Getting immudb Running: Kubernetes
For Kubernetes users, the process is simplified with Helm:
bash
helm repo add immudb https://packages.codenotary.org/helm
helm repo update
helm install immudb immudb --generate-name
Using Subfolders
The immudb Helm chart creates a persistent volume for storing databases, using subdirectories to avoid confusion with ext4 volumes. Adjust this if needed:
bash
# When upgrading, you can set the volumeSubPath to false
--set volumeSubPath.enabled=false
Enabling Amazon S3 Storage
immudb can utilize Amazon S3 for data storage. Here’s how you can enable it:
bash
export IMMUDB_S3_STORAGE=true
export IMMUDB_S3_ACCESS_KEY_ID=
export IMMUDB_S3_SECRET_KEY=
export IMMUDB_S3_BUCKET_NAME=
export IMMUDB_S3_LOCATION=
export IMMUDB_S3_PATH_PREFIX=testing-001
export IMMUDB_S3_ENDPOINT=https:$IMMUDB_S3_BUCKET_NAME.s3.$IMMUDB_S3_LOCATION.amazonaws.com
Troubleshooting
While everything should run smoothly, you might encounter some challenges. Here are common issues and suggestions to resolve them:
- It won’t start up: Ensure all dependencies are correctly installed and that the binary has correct permissions (use chmod). If using Docker, check that the ports are not in use.
- Connection problems: Verify your network settings and ensure your firewall is allowing traffic through the relevant ports.
- AWS S3 storage issues: Make sure your AWS credentials are valid and that your settings (bucket name, location) are correctly configured.
If you have further questions or issues, you can always check the documentation at immudb documentation. For more insights, updates, or to collaborate on AI development projects, stay connected with fxis.ai.
Conclusion
At fxis.ai, we believe that such advancements are crucial for the future of AI, as they enable more comprehensive and effective solutions. Our team is continually exploring new methodologies to push the envelope in artificial intelligence, ensuring that our clients benefit from the latest technological innovations.