<ruby id="bdb3f"></ruby>

    <p id="bdb3f"><cite id="bdb3f"></cite></p>

      <p id="bdb3f"><cite id="bdb3f"><th id="bdb3f"></th></cite></p><p id="bdb3f"></p>
        <p id="bdb3f"><cite id="bdb3f"></cite></p>

          <pre id="bdb3f"></pre>
          <pre id="bdb3f"><del id="bdb3f"><thead id="bdb3f"></thead></del></pre>

          <ruby id="bdb3f"><mark id="bdb3f"></mark></ruby><ruby id="bdb3f"></ruby>
          <pre id="bdb3f"><pre id="bdb3f"><mark id="bdb3f"></mark></pre></pre><output id="bdb3f"></output><p id="bdb3f"></p><p id="bdb3f"></p>

          <pre id="bdb3f"><del id="bdb3f"><progress id="bdb3f"></progress></del></pre>

                <ruby id="bdb3f"></ruby>

                ThinkChat2.0新版上線,更智能更精彩,支持會話、畫圖、視頻、閱讀、搜索等,送10W Token,即刻開啟你的AI之旅 廣告
                **1、docker 啟動報錯:** ~~~ Dec 5 16:15:31 WLWHDX50 docker-storage-setup: INFO: Waiting for device /dev/mapper/docker--vg-docker--pool to be available. Wait time remaining is 5 seconds Dec 5 16:15:36 WLWHDX50 docker-storage-setup: INFO: Timed out waiting for device /dev/mapper/docker--vg-docker--pool Dec 5 16:15:36 WLWHDX50 docker-storage-setup: ERROR: Already configured thin pool /dev/mapper/docker--vg-docker--pool is not available. If thin pool exists and is taking longer to activate, set DEVICE_WAIT_TIMEOUT to a higher value and retry. If thin pool does not exist any more, remove /etc/sysconfig/docker-storage and retry ~~~ /etc/sysconfig/docker-storage 配置文件制定pool,但是docker的版本不相同,會導致啟動報錯,可以將配置刪除掉。再次啟動 **2、docker啟動報錯:** ~~~ Dec 14 18:08:33 WLWHDX50 docker-storage-setup: Logical volume docker-vg/docker-pool changed. Dec 14 18:08:33 WLWHDX50 systemd: Started Docker Storage Setup. Dec 14 18:08:33 WLWHDX50 systemd: Starting Docker Application Container Engine... Dec 14 18:08:33 WLWHDX50 journal: Forwarding stdin to journald using Priority Informational and tag docker Dec 14 18:08:34 WLWHDX50 kernel: device-mapper: table: 253:5: thin: Couldn't open thin internal device Dec 14 18:08:34 WLWHDX50 kernel: device-mapper: ioctl: error adding target to table Dec 14 18:08:34 WLWHDX50 journal: time="2017-12-14T18:08:34.027979062+08:00" level=fatal msg="Error starting daemon: error initializing graphdriver: Base Device UUID and Filesystem verification failed.Error running deviceCreate (ActivateDevice) dm_task_run failed" Dec 14 18:08:34 WLWHDX50 systemd: Started Docker Application Container Engine. ~~~ 解決思路: `cat /var/lib/docker/devicemapper/metadata/deviceset-metadata` 中的BaseDeviceUUID與現主機的不通導致。 將/var/lib/docker/下的所有東西清理掉: `rm -rf /var/lib/docker/` 重啟docker `systemctl restart docker` 原因:之前安裝過1.12版本的docker,啟動成功過,劃分過vg-pool。卸載后再安裝1.9.1版本的docker啟動會報錯。
                  <ruby id="bdb3f"></ruby>

                  <p id="bdb3f"><cite id="bdb3f"></cite></p>

                    <p id="bdb3f"><cite id="bdb3f"><th id="bdb3f"></th></cite></p><p id="bdb3f"></p>
                      <p id="bdb3f"><cite id="bdb3f"></cite></p>

                        <pre id="bdb3f"></pre>
                        <pre id="bdb3f"><del id="bdb3f"><thead id="bdb3f"></thead></del></pre>

                        <ruby id="bdb3f"><mark id="bdb3f"></mark></ruby><ruby id="bdb3f"></ruby>
                        <pre id="bdb3f"><pre id="bdb3f"><mark id="bdb3f"></mark></pre></pre><output id="bdb3f"></output><p id="bdb3f"></p><p id="bdb3f"></p>

                        <pre id="bdb3f"><del id="bdb3f"><progress id="bdb3f"></progress></del></pre>

                              <ruby id="bdb3f"></ruby>

                              哎呀哎呀视频在线观看