-
Notifications
You must be signed in to change notification settings - Fork 462
Use agent docker image #10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
586f113
155c2cf
602aa21
8c44c8a
9ad1f35
a6ff867
5be35fb
8c4fed1
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,11 +1,26 @@ | ||
Firstly, refresh docker images: | ||
Before using the Package Registry, remember to `mage build` the project to prepare the volume with packages | ||
(`public` directory). | ||
|
||
Refresh docker images: | ||
|
||
```bash | ||
$ docker-compose -f snapshot.yml pull | ||
``` | ||
|
||
Run docker containers: | ||
Run docker containers (Elasticsearch, Kibana, Package Registry): | ||
|
||
```bash | ||
$ docker-compose -f snapshot.yml -f local.yml up --force-recreate | ||
``` | ||
|
||
... or with Elastic Agent: | ||
|
||
```bash | ||
$ docker-compose -f snapshot.yml -f local.yml -f agent.yml up --force-recreate | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Would be nice to have a mage command for this, easier to remember (at least for me). There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Well it all depends what do you need, either entire fleet with enrolled agent or you prefer to keep the agent aside on your host. I can add one or two default mage targets, but it will limit configurability of available docker-compose options. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Lets wait with it and see what most of us use frequently. |
||
``` | ||
|
||
Use this command to spawn more agents: | ||
|
||
```bash | ||
$ docker-compose -f snapshot.yml -f local.yml -f agent.yml up --scale elastic-agent=10 --no-recreate -d | ||
``` |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
# This should start the environment with the latest snapshots. | ||
|
||
version: '2.3' | ||
services: | ||
elastic-agent: | ||
image: docker.elastic.co/beats/elastic-agent:8.0.0-SNAPSHOT | ||
depends_on: | ||
elasticsearch: | ||
condition: service_healthy | ||
kibana: | ||
condition: service_healthy | ||
environment: | ||
- "FLEET_ENROLL=1" | ||
- "FLEET_SETUP=1" | ||
- "KIBANA_HOST=http://kibana:5601" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First time I run this I got:
I assume the timeout was too low.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm.. you can try to wipe out docker images. Anyway, this one is weird. If it's not a one-time issue, would be good to reproduce it.