localstack-extensions
localstack-extensions copied to clipboard
Fixing "ModuleNotFoundError: No module named 'flask'"
Due to a recent change in our packaging, you might notice the following exception in your logs when starting LocalStack with an Extension.
ModuleNotFoundError: No module named 'flask'
To fix this simply:
- clear the directory that is mounted into the LocalStack container at
/var/lib/localstack
- pull the latest image
- restart the LocalStack container
- re-install any extensions you were using if you're not using
EXTENSION_AUTO_INSTALL