[[["容易理解","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-01 (世界標準時間)。"],[],[],null,["You must configure the base operating system of your node machines to use\nGoogle Distributed Cloud. This page contains the steps you need to take to complete the\nneeded configuration. For more information about troubleshooting\nGoogle Distributed Cloud, see the\n[troubleshooting guides](/kubernetes-engine/distributed-cloud/bare-metal/docs/troubleshooting/known-issues).\n\nBefore you begin\n\nEnsure you are using a supported version of your operating system. For a list of\nsupported versions, see\n[Select your operating system](/kubernetes-engine/distributed-cloud/bare-metal/docs/installing/os-reqs).\n\nEnable BPF Just In Time compiler\n\nThe kernel for your operating system must have the BPF Just In Time compiler\noption enabled (`CONFIG_BPF_JIT=y`).\n\n- To find out whether this option is enabled, run the following command:\n\n grep CONFIG_BPF_JIT /boot/config-$(uname -r)\n\nValidate the package manager\n\nEnsure that you have your RedHat username and password, and that you have root\naccess to the machines you're configuring. Validate Package manager with the\nfollowing steps:\n\n1. If you haven't registered your operating system, register with RedHat using\n your RedHat username and password to download updates:\n\n sudo subscription-manager register\n\n sudo subscription-manager refresh\n\n sudo subscription-manager attach --auto\n\n2. Check for updates:\n\n sudo dnf check-update\n\n Ensure the output has no errors and includes the last metadata expiration\n check. For example: \n\n Updating Subscription Management repositories.\n ...\n # Last metadata expiration check: ...\n ...\n\nConfigure or disable firewalld\n\nFirewalld can be configured\nfor use with Google Distributed Cloud or disabled. For information on configuring\nfirewalld, see\n[Configure firewalld ports](/kubernetes-engine/distributed-cloud/bare-metal/docs/concepts/network-reqs#configuring_firewalld_ports)\non the Network requirements page.\n\nThe following instructions disable firewalld.\n\n1. Disable firewalld:\n\n sudo systemctl stop firewalld\n\n sudo systemctl disable firewalld\n\n2. Check the status of firewalld to ensure it is disabled:\n\n sudo systemctl status firewalld | grep \"Active\"\n # Output\n # Active: inactive (dead)\n\nConfigure Docker on your workstation **Note:** The workstation running `bmctl` needs non-root user access to Docker to start the temporary bootstrap (kind) cluster during installation. To enable non-root user access to Docker, go to [Manage Docker as a non-root user](https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user).\n\nFollow these steps to manually install Docker:\n\n1. Remove any previous Docker version:\n\n sudo dnf remove docker \\\n docker-client \\\n docker-client-latest \\\n docker-common \\\n docker-latest \\\n docker-latest-logrotate \\\n docker-logrotate \\\n docker-engine\n\n2. Remove podman-manpages:\n\n sudo dnf remove podman-manpages\n\n3. Install Docker 20.10.0+:\n\n sudo dnf install -y yum-utils\n\n sudo yum-config-manager \\\n --add-repo \\\n https://download.docker.com/linux/rhel/docker-ce.repo\n\n sudo dnf install -y --allowerasing docker-ce docker-ce-cli containerd.io\n\n sudo systemctl start docker\n\n4. Verify that you are now running version 20.10.0+:\n\n sudo docker version\n\n5. Compare your output with the following example to ensure the Client and\n Server versions are 20.10.0+:\n\n Client: Docker Engine - Community\n Version: 25.0.3\n ...\n Server: Docker Engine - Community\n Engine:\n Version: 25.0.3\n\n6. Verify Docker runs:\n\n docker run hello-world\n\n You should see something similar to this: \n\n Hello from Docker!\n\n This message shows that your installation appears to be working correctly.\n\nSet up time synchronization\n\nTime synchronization consists of setting the clocks on your node machines, using\na designated external time reference. Time synchronization is important for\ntime-sentive cluster activities, such as event logging and metrics collection.\nThe kernel of your node machine controls the clock in containers that run on the\nnode. To ensure proper time synchronization, install a network time protocol\n(NTP) service on your machines, using any of the available services:\n[`chrony`](https://chrony.tuxfamily.org/), `systemd-timesyncd`,\n`ntp`, or `ntpdate`. Run `timedatectl` to verify the system clock is\nsynchronized. The output of `timedatectl` should contain the following status: \n\n System clock synchronized: yes\n\nEnsure Linux kernel `inotify` limits are at or higher than minimum\n\nFor machines running RHEL 9 and 8.10, Linux kernel `inotify` limits\nfor maximum user instances and user watches must be greater than or equal to the\nfollowing:\n\n- `fs.inotify.max_user_instances`: `8192`\n- `fs.inotify.max_user_watches`: `524288`\n\nEnsure these values are set correctly on your node machines:\n\n1. Check the value of `max_user_instances`:\n\n cat /proc/sys/fs/inotify/max_user_instances\n\n2. If needed, update `max_user_instances` to the minimum value:\n\n echo 'fs.inotify.max_user_instances=8192' | sudo tee --append /etc/sysctl.conf\n\n3. Check the value of `max_user_watches`:\n\n cat /proc/sys/fs/inotify/max_user_watches\n\n4. If needed, update `max_user_watches` to the minimum value:\n\n echo 'fs.inotify.max_user_watches=524288' | sudo tee --append /etc/sysctl.conf\n\n5. If you updated either value, reboot the machine.\n\nBest Practices\n\nTo simplify installation, we recommend that you configure RHEL using a minimal\ninstallation with headless management. Also, be sure to enable your\n[network connection](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_basic_system_settings/assembly_configuring-and-managing-network-access_configuring-basic-system-settings)\nand either use the default DHCP or provide a valid, static IP address and\nnetwork information. Ensure that the machine can connect to\n[the required external resources](/kubernetes-engine/distributed-cloud/bare-metal/docs/installing/proxy#prerequisites),\nsuch as `cloud.google.com`.\n\nIf Docker fails to run, check that the Docker daemon is running with the following command: \n\n sudo systemctl start docker"]]