# Stockage non pris en charge et vérification du dernier lanceur créent une boucle infinie

**URL:** <https://meta.discourse.org/t/unsupported-storage-and-checking-latest-launcher-create-infinite-loop/117014>\
**Category:** Product Support\
**Created:** [Mai 6, 2019, 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:** 5

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [Mai 9, 2019, 5:48 UTC](https://meta.discourse.org/t/unsupported-storage-and-checking-latest-launcher-create-infinite-loop/117014/5 "2019-05-09T05:48:20Z")

</div>

Our white list looks good to me, maybe even a bit too wide.

I am not sure if we should keep carrying overlay1 as a supported driver. Also btrfs can be somewhat dodgy.

@saj do you think we should drop `overlay` from our supported list? (keeping `overlay2`)

---

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