このコンテンツは選択した言語では利用できません。

Chapter 4. Migrating MicroShift from RHEL for Edge to image mode for RHEL


To migrate MicroShift from Red Hat Enterprise Linux for Edge (RHEL for Edge), embed MicroShift on a new image mode for RHEL image.

4.1. Migrating MicroShift to image mode for RHEL

Migrating MicroShift from a Red Hat Enterprise Linux for Edge (RHEL for Edge) system to a image mode for RHEL system requires building a new image mode for RHEL image containing the required version of MicroShift and any associated optional RPMs.

See the Red Hat Enterprise Linux (RHEL) documentation for general instructions on migrating RHEL for Edge systems to image mode for RHEL using the bootc switch command. Plan the upgrade process carefully. The following tips apply:

  • Follow the instructions in the RHEL documentation for converting rpm-ostree blueprint files to image mode container files.
  • You can use the rpm-ostree compose container-encapsulate image-compose command to create a base container image that can be used for bootc container builds. Then you can derive and familiarize yourself with an image mode for RHEL image that is based on existing ostree commits.
  • To fully adopt image mode for RHEL, define a container build pipeline.
  • Plan for UID and GID drift because RHEL for Edge and image mode for RHEL are not derived from the same parent image. See the RHEL documentation for more information.

4.1.1. Working around UID and GID drift when migrating to image mode for RHEL

If you do not re-install operating systems that are running MicroShift, you must use a workaround for a possible UID and GID drift during the migration process. One way to solve this problem is to add systemd units that apply the necessary fixes before the affected system services are started.

Prerequisites

  • You have an existing RHEL for Edge deployment running MicroShift.
  • You have root access to the build host.
  • You have an image that you want to deploy.

Procedure

  • Solve the potential UID or GID drift for the Open vSwitch (OVS) systemd service, ovsdb-server.service, by adding the following command to the MicroShift image-build procedure:

    # Install systemd configuration drop-ins to fix potential permission problems when upgrading from rpm-ostree commits to image mode container layers
    RUN mkdir -p /usr/lib/systemd/system/ovsdb-server.service.d && \
        cat > /usr/lib/systemd/system/ovsdb-server.service.d/microshift-ovsdb-ownership.conf <<'EOF'
    # The openvswitch database files must be owned by the appropriate user and its primary group. That the user and its group can be overwritten, recreate them.
    [Service]
    ExecStartPre=/bin/sh -c '/bin/getent passwd openvswitch >/dev/null || useradd -r openvswitch'
    ExecStartPre=/bin/sh -c '/bin/getent group hugetlbfs >/dev/null || groupadd -r hugetlbfs'
    ExecStartPre=/sbin/usermod -a -G hugetlbfs openvswitch
    ExecStartPre=/bin/chown -Rhv openvswitch. /etc/openvswitch
    EOF
    Copy to Clipboard Toggle word wrap
    Important

    After the MicroShift migration to image mode for RHEL is complete, this workaround is not needed and can be removed.

Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

Theme

© 2026 Red Hat
トップに戻る