Skip to content
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

Cherry-pick #14424 to 7.5: Remove add_docker_metadata from Functionbeat configuration #14480

Merged
merged 1 commit into from
Nov 22, 2019

Conversation

kvch
Copy link
Contributor

@kvch kvch commented Nov 12, 2019

Cherry-pick of PR #14424 to 7.5 branch. Original message:

The PR #13374 adds add_docker_metadata for all Beats. However, this results in the following error in Functionbeat when deployed to AWS:

Exiting: error initializing processors: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Thus, the function fails to start and process messages.

This PR removes the processor from the configuration of Functionbeat. So the function is able to start with the default processor configuration.

…4424)

The PR elastic#13374 adds `add_docker_metadata` for all Beats. However, this results in the following error in Functionbeat when deployed to AWS:
```
Exiting: error initializing processors: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
```

Thus, the function fails to start and process messages.

This PR removes the processor from the configuration of Functionbeat. So the function is able to start with the default processor configuration.
(cherry picked from commit d9a4c9c)
@kvch kvch merged commit eb0f988 into elastic:7.5 Nov 22, 2019
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…4424) (elastic#14480)

The PR elastic#13374 adds `add_docker_metadata` for all Beats. However, this results in the following error in Functionbeat when deployed to AWS:
```
Exiting: error initializing processors: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
```

Thus, the function fails to start and process messages.

This PR removes the processor from the configuration of Functionbeat. So the function is able to start with the default processor configuration.
(cherry picked from commit c25f71a)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants