Update documentation to include Podman as an alternative to Docker

Author: teresaromero

README.md

@@ -490,6 +490,8 @@ You can run your own custom images for Elasticsearch, Kibana or Elastic Agent, s
 
 Be aware that a common issue while trying to boot up the stack is that your Docker environments settings are too low in terms of memory threshold.
 
+You can use Podman instead of Docker, see [this document](./docs/howto/use_podman.md)
+
 For details on how to connect the service with the Elastic stack, see the [service command](https://github.com/elastic/elastic-package/blob/main/README.md#elastic-package-service).
 
 ### `elastic-package stack down`
@@ -542,6 +544,8 @@ You can run your own custom images for Elasticsearch, Kibana or Elastic Agent, s
 
 Be aware that a common issue while trying to boot up the stack is that your Docker environments settings are too low in terms of memory threshold.
 
+You can use Podman instead of Docker, see [this document](./docs/howto/use_podman.md)
+
 To expose local packages in the Package Registry, build them first and boot up the stack from inside of the Git repository containing the package (e.g. elastic/integrations). They will be copied to the development stack (~/.elastic-package/stack/development) and used to build a custom Docker image of the Package Registry. Starting with Elastic stack version >= 8.7.0, it is not mandatory to be available local packages in the Package Registry to run the tests.
 
 For details on how to connect the service with the Elastic stack, see the [service command](https://github.com/elastic/elastic-package/blob/main/README.md#elastic-package-service).

cmd/stack.go

@@ -35,6 +35,8 @@ You can run your own custom images for Elasticsearch, Kibana or Elastic Agent, s
 
 Be aware that a common issue while trying to boot up the stack is that your Docker environments settings are too low in terms of memory threshold.
 
+You can use Podman instead of Docker, see [this document](./docs/howto/use_podman.md)
+
 For details on how to connect the service with the Elastic stack, see the [service command](https://github.com/elastic/elastic-package/blob/main/README.md#elastic-package-service).`
 
 const stackUpLongDescription = `Use this command to boot up the stack locally.
@@ -45,6 +47,8 @@ You can run your own custom images for Elasticsearch, Kibana or Elastic Agent, s
 
 Be aware that a common issue while trying to boot up the stack is that your Docker environments settings are too low in terms of memory threshold.
 
+You can use Podman instead of Docker, see [this document](./docs/howto/use_podman.md)
+
 To expose local packages in the Package Registry, build them first and boot up the stack from inside of the Git repository containing the package (e.g. elastic/integrations). They will be copied to the development stack (~/.elastic-package/stack/development) and used to build a custom Docker image of the Package Registry. Starting with Elastic stack version >= 8.7.0, it is not mandatory to be available local packages in the Package Registry to run the tests.
 
 For details on how to connect the service with the Elastic stack, see the [service command](https://github.com/elastic/elastic-package/blob/main/README.md#elastic-package-service).

docs/howto/use_podman.md

@@ -1,8 +1,8 @@
 # How to Develop Using Podman Instead of Docker
 
-`elastic-package` runs Docker commands, if you are using Podman instead of Docker you might come accross some errors if Podman is not well configured.
+`elastic-package` Docker-based commands should work out of the box using Podman instead of Docker.
 
-Podman provides a Docker-compatible CLI. You can setup Podman so it runs whenever the Docker commands are run, [following the migration guide](https://podman-desktop.io/docs/migrating-from-docker/managing-docker-compatibility).
+Check you have Podman configured [following the migration guide](https://podman-desktop.io/docs/migrating-from-docker/managing-docker-compatibility)
 
 - [Podman Official Documentation](https://docs.podman.io/)
 - [Podman vs Docker Comparison](https://podman.io/getting-started/)