# 非対応のストレージと最新ランチャーのチェックで無限ループが発生

**URL:** <https://meta.discourse.org/t/unsupported-storage-and-checking-latest-launcher-create-infinite-loop/117014>\
**Category:** Product Support\
**Created:** [2019 年 5 月 6 日午後 10:57 UTC](https://meta.discourse.org/t/unsupported-storage-and-checking-latest-launcher-create-infinite-loop/117014 "2019-05-06T22:57:20Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![saj](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/saj/32/523935_2.png) [@saj](https://meta.discourse.org/u/saj)\
**Post date:** [2019 年 5 月 10 日午後 7:34 UTC](https://meta.discourse.org/t/unsupported-storage-and-checking-latest-launcher-create-infinite-loop/117014/7 "2019-05-10T19:34:32Z")

</div>

Yes, I think it would be reasonable to drop the `overlay` storage driver from the whitelist. 👍

Foremost in my mind was not unduly inconveniencing users on enterprise distros. Docker Inc. appear to have dropped their support for all platforms but the following:

- Debian 9 (and later)
- EL7
- Ubuntu 16.04 (and later)

The kernels in these distributions should support `overlay2`. I can’t think of a reason why someone would choose to use the older `overlay` driver when their system meets `overlay2` requirements.

---

_[View the full topic](https://meta.discourse.org/t/unsupported-storage-and-checking-latest-launcher-create-infinite-loop/117014)._