Send feedback
Install AlloyDB Omni
Stay organized with collections
Save and categorize content based on your preferences.
This quickstart shows you how to install AlloyDB Omni that can run
in any UNIX-based environment which supports container runtimes.
For an overview of AlloyDB Omni, see AlloyDB Omni overview .
Before you begin
Note: You can run AlloyDB Omni on macOS. However,
AlloyDB Omni in a Docker container on macOS uses Docker's
compatibility layer, which can result in reduced performance compared to
running it directly on Linux.
Media
Download locations and installation guides
Deployment to
Debian image
DockerHub (tags)
Docker , Podman . You
can run these containerization tools as a container in any virtual machine
(VM).
UBI Image (Red Hat)
Red Hat Ecosystem Catalog
Red Hat environment. Run this as a container.
Fulfill hardware and software requirements
Make sure that you meet the following minimum hardware and software requirements:
OS/Platform
Minimum hardware
Minimum software
Linux
x86-64 or Arm (*) CPU with AVX2 support
2 GB of RAM
10 GB of disk space
Debian based OS (Ubuntu, etc.), RHEL 8 or 9
Linux kernel version 5.3 or higher
Cgroupsv2 enabled
Docker Engine 20.10+ or Podman 4.2.0+
macOS
Intel CPU with AVX2 support or M-chip
2GB of RAM
10 GB of disk space
Docker Desktop 4.20 or higher
(*) AlloyDB Omni supports Arm (Preview ).
Verify that cgroupsv2 is enabled
To determine whether cgroupsv2 is enabled on your machine, run the following command:
grep cgroup /proc/filesystems
If your machine supports cgroupsv2, you see the following output:
nodev cgroup
nodev cgroupsv2
If your machine doesn't support cgroupsv2, you see the following output:
nodev cgroup
Install a container runtime
Install a container runtime like Docker
or Podman . AlloyDB Omni
runs in a container.
Install AlloyDB Omni using Docker
Root access isn't required for installing AlloyDB Omni.
Docker
Use the docker run
command to create a new container with AlloyDB Omni named my-omni
:
docker run --name my-omni \
-e POSTGRES_PASSWORD = NEW_PASSWORD \
-d google/alloydbomni:15
Replace NEW_PASSWORD
with a password to assign the new container's postgres
user after its creation.
Note: By default, AlloyDB Omni stores your data on the container itself, and not on your host file system. The data directory is deleted once you delete your AlloyDB Omni container. To mount a data directory stored on your host file system, see instructions in Customize your AlloyDB Omni installation .
Connect to containerized AlloyDB Omni using psql
:
docker exec -it my-omni psql -h localhost -U postgres
The terminal window displays psql
login text that ends with a
postgres=#
prompt.
Podman
Use the docker run
command to create a new container with AlloyDB Omni named my-omni
:
podman run --name my-omni \
-e POSTGRES_PASSWORD = NEW_PASSWORD \
-d google/alloydbomni:15
Replace NEW_PASSWORD
with a password to assign the new container's postgres
user after its creation.
Note: By default, AlloyDB Omni stores your data on the container itself, and not on your host file system. The data directory is deleted once you delete your AlloyDB Omni container. To mount a data directory stored on your host file system, see instructions in Customize your AlloyDB Omni installation .
Connect to containerized AlloyDB Omni using psql
:
podman exec -it my-omni psql -h localhost -U postgres
The terminal window displays psql
login text that ends with a
postgres=#
prompt.
Clean up
To clean up the AlloyDB Omni container you created during this quickstart, use these steps:
Docker
Stop your AlloyDB Omni container named my-omni
:
docker container stop my-omni
Delete your AlloyDB Omni container named my-omni
:
docker container rm my-omni
Podman
Stop your AlloyDB Omni container named my-omni
:
podman container stop my-omni
Delete your AlloyDB Omni container named my-omni
:
podman container rm my-omni
For instructions how to install AlloyDB Omni in a new container for production usage, go to the Customize your AlloyDB Omni installation page.
What's next
Send feedback
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License , and code samples are licensed under the Apache 2.0 License . For details, see the Google Developers Site Policies . Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-07-15 UTC.
Need to tell us more?
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-15 UTC."],[[["AlloyDB Omni can be installed in any UNIX-based environment that supports container runtimes, provided you have an agreement with Google governing Google Cloud offerings."],["The minimum requirements for running AlloyDB Omni include either an x86-64 or Arm CPU with AVX2 support, 2 GB of RAM, 10 GB of disk space, and a compatible operating system such as Linux or macOS."],["AlloyDB Omni installation requires a container runtime like Docker or Podman, and can be done using the `docker run` or `podman run` command to create a new container."],["By default, AlloyDB Omni stores data within the container, which will be deleted upon container removal, but users can configure it to store data on the host file system."],["To clean up the AlloyDB Omni container, you need to stop and then delete it using either `docker container` or `podman container` commands, depending on the runtime you utilized."]]],[]]