You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,6 +39,8 @@ Run the `help` command and see available commands:
39
39
elastic-package help
40
40
```
41
41
42
+
Some sub-commands are Docker-based, check you also have Docker installed. In case you are using Podman Desktop, check [this guide](./docs/howto/use_podman.md) to make it compatible.
43
+
42
44
## Development
43
45
44
46
Even though the project is "go-gettable", there is the [`Makefile`](./Makefile) present, which can be used to build,
@@ -490,6 +492,8 @@ You can run your own custom images for Elasticsearch, Kibana or Elastic Agent, s
490
492
491
493
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.
492
494
495
+
You can use Podman Desktop instead of Docker, see [this document](./docs/howto/use_podman.md)
496
+
493
497
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).
494
498
495
499
### `elastic-package stack down`
@@ -542,6 +546,8 @@ You can run your own custom images for Elasticsearch, Kibana or Elastic Agent, s
542
546
543
547
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.
544
548
549
+
You can use Podman Desktop instead of Docker, see [this document](./docs/howto/use_podman.md)
550
+
545
551
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.
546
552
547
553
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).
@@ -850,7 +856,7 @@ There are available some environment variables that could be used to change some
850
856
-`ELASTIC_PACKAGE_DATA_HOME`: Custom path to be used for `elastic-package` data directory. By default this is `~/.elastic-package`.
851
857
852
858
- Related to the build process:
853
-
-`ELASTIC_PACKAGE_REPOSITORY_LICENSE`: Path to the default repository license.
859
+
-`ELASTIC_PACKAGE_REPOSITORY_LICENSE`: Path to the default repository license. This path should be relative to the repository root.
854
860
-`ELASTIC_PACKAGE_LINKS_FILE_PATH`: Path to the links table file (e.g. `links_table.yml`) with the link definitions to be used in the build process of a package.
0 commit comments