# XBlock SDK – Docker – workbench\_database

**URL:** <https://discuss.openedx.org/t/xblock-sdk-docker-workbench-database/4204>\
**Category:** Development\
**Created:** [February 4, 2021, 4:24pm UTC](https://discuss.openedx.org/t/xblock-sdk-docker-workbench-database/4204 "2021-02-04T16:24:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zachary\_Trabookis](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/zachary_trabookis/32/753_2.png) [@Zachary\_Trabookis](https://discuss.openedx.org/u/Zachary_Trabookis)\
**Post date:** [February 4, 2021, 4:24pm UTC](https://discuss.openedx.org/t/xblock-sdk-docker-workbench-database/4204/1 "2021-02-04T16:24:34Z")

</div>

I’m trying to following the directions [GitHub - edx/xblock-sdk: Workbench and example xblocks](https://github.com/edx/xblock-sdk#docker) for setting up the XBlock SDK, however, I get an error about `no such table: workbench_xblockstate`.

After further investigation I don’t see a `SQLITE_DB=var/workbench.db` as mentioned here [xblock-sdk/Makefile at master · edx/xblock-sdk · GitHub](https://github.com/edx/xblock-sdk/blob/master/Makefile#L19)

The directions here mention setting up a connection to the MySQL devstack database using `WORKBENCH_DATABASES`.

> **[edx/xblock-sdk - Using the workbench](https://github.com/edx/xblock-sdk#using-the-workbench)**
>
> Workbench and example xblocks. Contribute to edx/xblock-sdk development by creating an account on GitHub.

After running `python manage.py migrate` we were able to provision the database tables on MySQL lite database. Is there any reason why we would want to use the MySQL devstack container rather than using the local MySQL lite provided by this XBlock SDK?

cc: @braden @arbrandes @jill @bsande6

---

<div class="post-metadata">

**Author:** ![arbrandes](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.openedx.org/arbrandes/32/158_2.png) [@arbrandes](https://discuss.openedx.org/u/arbrandes)\
**Post date:** [February 5, 2021, 10:58am UTC](https://discuss.openedx.org/t/xblock-sdk-docker-workbench-database/4204/2 "2021-02-05T10:58:45Z")

</div>

@Zachary_Trabookis, let me refer you to Braden’s comment from [a couple of months back](https://discuss.openedx.org/t/xblock-sdk-setting-entry-points-for-virtenv/3590/2):

> [@Xblock SDK: Setting entry points for virtenv](https://discuss.openedx.org/t/xblock-sdk-setting-entry-points-for-virtenv/3590/2):
>
> It’s probably worth mentioning that as an XBlock developer, I personally don’t use the XBlock SDK anymore, and just develop and test my XBlock directly in Studio+LMS. The XBlock SDK is useful for learning XBlocks and testing very simple XBlocks but for anything complex it acts differently than the LMS so is less useful.

In other words, unless you have a strong reason for using the SDK, you should probably be developing your XBlock against edx-platform in the devstack.