# Things that don't seem to work (yet) on DigitalOcean racks

**URL:** <https://community.convox.com/t/things-that-dont-seem-to-work-yet-on-digitalocean-racks/763>\
**Category:** Rack (Version 3)\
**Created:** [July 29, 2020, 10:27am UTC](https://community.convox.com/t/things-that-dont-seem-to-work-yet-on-digitalocean-racks/763 "2020-07-29T10:27:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![crohr](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.convox.com/crohr/32/29_2.png) [@crohr](https://community.convox.com/u/crohr)\
**Post date:** [July 29, 2020, 10:27am UTC](https://community.convox.com/t/things-that-dont-seem-to-work-yet-on-digitalocean-racks/763/1 "2020-07-29T10:27:05Z")

</div>

Rack install on DigitalOcean went fine, but:

- `convox rack params` doesn’t return anything.

- `convox build` fails intermittently with `error creating overlay mount to /var/lib/docker/overlay2/20599d175f2edc99dd26da76b3a6f0fef92ad9214a8402b6fde02463d4ba876d/merged: device or resource busy`

- volumes don’t seem to work. On the first deploy the Persistent Volume Claims are created, but DO doesn’t dynamically provision the corresponding Persistent Volume.

- running a one-off process doesn’t seem to work (possibly due to the volume issue).

- it’s hard to know which resource types are available for which provider, and how they map to managed services (or not).