You can also use docker directly and use the following command to get started with localstackĭocker run -rm -it -p 4566:4566 -p 4571:4571 localstack/localstack Note that this will require additional dependencies, and is not supported on some operating systems, including Windows. Note: Although we strongly recommend to use Docker, the infrastructure can also be spun up directly on the host machine using the -host startup flag. Note: By default, LocalStack uses the image tagged latest that is cached on your machine, and will not pull the latest image automatically from Docker Hub (i.e., the image needs to be pulled manually if needed). Please also refer to the USE_LIGHT_IMAGE configuration below. In case you need the full set of dependencies, the localstack/localstack-full image can be used instead. (Note that the localstack/localstack-light image alias may get removed in the future). Note: From onwards, the default image localstack/localstack in Docker Hub refers to the "light version", which has some large dependency files like Elasticsearch removed (and lazily downloads them, if required). (Note that on MacOS you may have to run TMPDIR=/private$TMPDIR localstack start -docker if $TMPDIR contains a symbolic link that cannot be mounted by Docker.) If you have problemswith permissions in MacOS X Sierra, install with pip install -user localstack Runningīy default, LocalStack is started inside a Docker container by running: Note: Please do not use sudo or the root user - LocalStackshould be installed and started entirely under a local non-root user. The easiest way to install LocalStack is via pip:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |