Looker에는 이미지 기반 형식(HTML 및 PNG 또는 PDF 파일)으로 데이터를 전송 또는 다운로드하고 용지 크기 및 테이블 확장과 같은 기능을 사용하려면 Chromium이라는 렌더링 소프트웨어가 필요합니다. 이 페이지에서는 고객이 호스팅하는 Looker 인스턴스에 렌더링 소프트웨어를 설치하는 방법을 설명합니다.
Chromium 렌더링은 페이지에서 요청한 모든 리소스가 완료될 때까지 기다린 후 Looker에 렌더링된 콘텐츠를 생성하라는 메시지를 '완료됨' 신호로 전송합니다. 이러한 리소스 요청 수와 빈도로 인해 일부 네트워크에서 요청을 악의적으로 신고하여 삭제할 수 있으며 이로 인해 렌더링된 작업이 지연됩니다.
Chromium 프로젝트는 Google Chrome의 독점적이지 않은 부분을 공유하기 위해 Google이 시작한 오픈소스 프로젝트입니다.
선택적 환경 변수를 설정한 후 Looker 애플리케이션을 다시 시작하여 적용합니다. 열려 있는 터미널 세션을 다시 시작하거나 셸 파일을 소스화하여 터미널이 새 구성을 읽도록 해야 할 수도 있습니다.
Chromium을 설치한 후 CHROMIUM_PATH 환경 변수를 설정하지 않은 경우 chromium --version를 실행하거나 (CHROMIUM_PATH 환경 변수를 설정하지 않은 경우) $CHROMIUM_PATH --version를 실행하면 (CHROMIUM_PATH 환경 변수를 설정한 경우) 올바른 응답을 받게 됩니다.
CHROMIUM_PID_DIR: 라이브러리가 Chromium PID 파일을 저장할 수 있는 경로이며 기본값은 Looker 애플리케이션 작업 디렉터리에 있는 chromium_pid_files입니다.
CHROMIUM_PORT_RANGE_START 및 CHROMIUM_PORT_RANGE_END: Chromium 애플리케이션에서 로컬 머신의 프로세스 간에 통신하려면 포트 범위가 필요합니다. 기본 범위는 40000~40500이지만, 두 환경 변수를 모두 설정하여 이 기본값을 재정의할 수 있습니다. 사용되지 않은 포트는 범위에서 무작위로 선택되며 단일 렌더링 기간에만 사용됩니다.
DISABLE_EXTERNAL_RENDER_ACCESS: 외부 또는 차단된 인터넷 액세스가 없는 고객이 호스팅하는 Looker 인스턴스 또는 서버의 관리자는 DISABLE_EXTERNAL_RENDER_ACCESS=true을 설정해야 합니다. 일반적으로 Chromium 렌더러는 페이지에서 요청한 모든 리소스가 완료되기를 기다린 후 렌더러가 '완료' 신호를 보내 Looker에게 콘텐츠를 생성하라는 메시지를 표시합니다. 이러한 요청 중 일부는 연결 부족으로 인해 중단되거나 시간 초과 또는 렌더링 시간이 매우 길어질 수 있습니다. 이 환경 변수를 true로 설정하면 렌더러가 모든 요청이 완료될 때까지 기다릴 수 없습니다. Looker Marketplace에서 설치된 일부 지도 시각화 및 커스텀 시각화에는 인터넷 액세스가 필요할 수 있습니다.
[[["이해하기 쉬움","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)"],[],[],null,["# Customer-hosted installation of rendering software\n\nLooker requires rendering software called Chromium to send or download data in image-based formats --- HTML and PNG or PDF files --- and to use features such as [Paper size](/looker/docs/scheduling-and-sending-dashboards#paper_size) and [Expand tables](/looker/docs/scheduling-and-sending-dashboards#expand_tables_to_show_all_rows). This page explains how to install rendering software on a customer-hosted instance of Looker.\n| **Note:** Chromium is already installed for Looker-hosted instances.\n\nChromium rendering waits for all resources that have been requested by the page to be completed before it sends the \"finished\" signal that prompts Looker to produce the rendered content. Because of the number and frequency of these resource requests, some networks can falsely flag the requests as malicious, causing them to drop, which will delay your rendered jobs.\n\nThe Chromium Project is an open source project that was started by Google to share the non-proprietary parts of Google Chrome.\n\nBefore you begin\n----------------\n\nBefore you install Chromium, learn more about the following topics:\n\n- [Chromium installation requirements and prerequisites](#chromium_installation_requirements_and_prerequisites)\n- [Things to know about installing Chromium on specific distributions](#things_to_know)\n- [Install font packages](#install_fonts)\n\n### Chromium installation requirements and prerequisites\n\nThis page provides example instructions for installing Chromium that are independent from a distribution type. You can also [download Chromium](https://chromium.googlesource.com/chromium/src/+/main/docs/linux/build_instructions.md) and then follow the remaining installation instructions on this page.\n\nTo run Chromium on a Looker instance, Chromium 97, Chromium 109, or Chromium 114 are required. Chromium must be installed into an executable path on the machine that hosts the Looker instance. The Looker application needs to access Chromium either by using the `chromium` command or by using a custom path that is set with the `CHROMIUM_PATH` \\[environment variable(#optional_chromium_environment_variables).\n\nIf you are installing Chromium on a clustered Looker installation, the Chromium version on each node must be fully identical. Even minor differences, such as different build numbers, can interfere with Looker's rendering capabilities.\n\n### Things to know about installing Chromium on specific distributions\n\nLooker supports release versions of all major enterprise Linux distributions, including Ubuntu (LTS releases), Debian 9+, RedHat Enterprise Linux (RHEL) 7+, CentOS 7+, and Amazon Linux.\n\nFor Ubuntu installations, you must install the Chromium web browser and then set an alias so that the Looker application can find the installation.\n\nFor Debian installations, Chromium requires Debian 9 (stretch) or later. If your Looker instance uses Docker with a bare-bones Debian installation, install [procps](https://gitlab.com/procps-ng/procps) and ensure that you are not running as root.\n\n### Install font packages\n\nA Microsoft OpenType font (OTF) package must be installed on the system for Chromium to start. OTF packages use `.otf` file extensions. You can download any OTF package, such as this [OTF package from Google Fonts](https://fonts.google.com).\n\nIf your data contains non-English characters, you must also install [the Google Noto Fonts package](https://fonts.google.com/noto) (which is several GB in size).\n\nAfter installing these packages, run the following commands: \n\n cd $HOME\n rm -rf /tmp/fonts\n\n\nInstalling Chromium\n-------------------\n\n| **Tip:** Don't install Chromium when you're logged in as the root user; instead use `sudo` to perform any steps that require elevated permissions. If you install Chromium while you are logged in as the root user, Looker might not be able to execute PDF or PNG rendering.\n\n1. To install Chromium, run the installation command that is applicable to your system. For example:\n\n apt-get update && apt-get install -y chromium-browser\n\n2. You must either alias `chromium-browser` as `chromium` or export the `CHROMIUM_PATH` environment variable. To alias `chromium-browser` as `chromium`, place the following in the shell file that is applicable to your system. For example:\n\n alias chromium='chromium-browser'\n\n To make this alias known to Looker, run this command on the command line: \n\n sudo ln -s /usr/bin/chromium-browser /usr/bin/chromium\n\n3. After you set any of the optional [environment variables](#optional_chromium_environment_variables), restart the Looker application so the variables can take effect. You may also need to restart any open terminal sessions, or source your shell file, to get the terminal to read the new configuration.\n\nAfter installing Chromium you should get a valid response from running `chromium --version` (if you have not set the `CHROMIUM_PATH` environment variable) or from running `$CHROMIUM_PATH --version` (if you have set the `CHROMIUM_PATH` environment variable).\n\n### Optional Chromium environment variables\n\n- `CHROMIUM_PATH`: Path to the Chromium binary, defaults to `chromium`.\n\n- `CHROMIUM_PID_DIR`: Path to where the library can store Chromium PID files, defaults to `chromium_pid_files` in the Looker application working directory.\n\n- `CHROMIUM_PORT_RANGE_START` \\& `CHROMIUM_PORT_RANGE_END`: The Chromium application needs a range of ports to communicate between processes on the local machine. The default range is 40000-40500 but you can override this default by setting both of these environment variables. Unused ports are selected at random from the range and are only used for the duration of a single render.\n\n- `DISABLE_EXTERNAL_RENDER_ACCESS`: Admins of customer-hosted Looker instances or servers that have no external or blocked internet access should set `DISABLE_EXTERNAL_RENDER_ACCESS=true`. Typically, the Chromium renderer will wait for all resources that are requested by the page to be completed before the renderer sends the \"finished\" signal that prompts Looker to produce the content. Some of these requests may be dropped because of a lack of connection, resulting in timeouts or very long render times. Setting this environment variable to `true` prevents the renderer from waiting for all requests to finish. Some map visualizations and some custom visualizations that are installed from the Looker Marketplace may require internet access."]]
