-
Notifications
You must be signed in to change notification settings - Fork 525
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
flag provided but not defined: -environment #14280
Labels
Comments
This was referenced Oct 7, 2024
This was referenced Oct 8, 2024
2 tasks
carsonip
added a commit
to carsonip/apm-server
that referenced
this issue
Oct 9, 2024
Unblock elastic#14292 to fix elastic#14280. Reverting beats instead of bumping beats to avoid elastic#14297.
This was referenced Oct 9, 2024
Merged
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
APM Server version (
apm-server version
): 8.x branch, 9.0 branchDescription of the problem including expected versus actual behavior:
On startup, apm-server will fail to start if
--environment
is passed. This causes docker images to fail as the entrypoint runs apm-server with--environment=container
.Steps to reproduce:
Please include a minimal but complete recreation of the problem,
including server configuration, agent(s) used, etc. The easier you make it
for us to reproduce it, the more likely that somebody will take the time to
look at it.
go run ./x-pack/apm-server --environment=container -e
Provide logs (if relevant):
The text was updated successfully, but these errors were encountered: