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
docker run -it \
--env HOME_PATH=/app \
-v <your-path>/app:/app <image-ID>
Run ls -la <your-path>/app/data/elastic-agent*/downloads; it only shows filebeat and metricbeat (after they have been downloaded by the agent); compare to downloads folder when exec into the docker container, which shows filebeat, metricbeat, heartbeat, endpoint-security, apm-server.
This is required for the elastic cloud setup, as a home path needs to be provided, and the apm-server needs to be bundled.
I have not checked whether this also occurs with another installation method.
When running the docker container and providing
--path.home
thedownloads
folder is empty.Reproduce:
exec {{ .BeatName }} container --path.home ${HOME_PATH} "$@"
ls -la <your-path>/app/data/elastic-agent*/downloads
; it only showsfilebeat
andmetricbeat
(after they have been downloaded by the agent); compare todownloads
folder when exec into the docker container, which showsfilebeat, metricbeat, heartbeat, endpoint-security, apm-server
.This is required for the elastic cloud setup, as a home path needs to be provided, and the apm-server needs to be bundled.
I have not checked whether this also occurs with another installation method.
cc @ruflin @michalpristas
The text was updated successfully, but these errors were encountered: