[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003eAlloyDB Omni is designed to run in containerized environments on any UNIX-based system, including Linux and macOS, that supports container runtimes.\u003c/p\u003e\n"],["\u003cp\u003eMinimum hardware requirements for running AlloyDB Omni include an x86-64 or Arm CPU with AVX2 support, 2 GB of RAM, and 10 GB of disk space.\u003c/p\u003e\n"],["\u003cp\u003eInstallation of AlloyDB Omni requires a container runtime like Docker or Podman, and you can set it up using the \u003ccode\u003edocker run\u003c/code\u003e or \u003ccode\u003epodman run\u003c/code\u003e commands.\u003c/p\u003e\n"],["\u003cp\u003eConnecting to the containerized AlloyDB Omni instance is done via \u003ccode\u003epsql\u003c/code\u003e after creating the container, and it can be managed and cleaned up using the \u003ccode\u003edocker\u003c/code\u003e or \u003ccode\u003epodman\u003c/code\u003e commands.\u003c/p\u003e\n"],["\u003cp\u003eData in AlloyDB Omni is by default stored within the container and will be deleted when the container is removed, however it is possible to mount a data directory stored on your host file system for production usage.\u003c/p\u003e\n"]]],[],null,[]]