added a docker-compose file to the main repo, and an explanation regarding its usage to the docs #306
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,73 @@ | ||
| version: '2' | ||
| services: | ||
| cassandra: | ||
| image: cassandra:3.11 | ||
| networks: | ||
| - jaeger | ||
| ports: | ||
| - "7000:7000" | ||
| - "7001:7001" | ||
| - "7199:7199" | ||
| - "9042:9042" | ||
| - "9160:9160" | ||
| restart: unless-stopped | ||
| volumes: | ||
| - cassandra-data:/var/lib/cassandra | ||
| - cassandra-logs:/var/log/cassandra | ||
| logging: | ||
| options: | ||
| max-size: 5m | ||
| environment: | ||
| MAX_HEAP_SIZE: 512M | ||
| HEAP_NEWSIZE: 100M | ||
| CASSANDRA_CLUSTER_NAME: "jaeger" | ||
| CASSANDRA_DC: "dc1" | ||
| CASSANDRA_RACK: "rack1" | ||
| CASSANDRA_ENDPOINT_SNITCH: "GossipingPropertyFileSnitch" | ||
| CASSANDRA_START_RPC: "true" | ||
| cassandra-scheme: | ||
| image: jaegertracing/jaeger-cassandra-schema:0.5 | ||
| networks: | ||
| - jaeger | ||
| depends_on: | ||
| - cassandra | ||
| jaeger-collector: | ||
| image: jaegertracing/jaeger-collector:0.5 | ||
| networks: | ||
| - jaeger | ||
| ports: | ||
| - "14267:14267" | ||
| - "14268:14268" | ||
| depends_on: | ||
| - cassandra-scheme | ||
| restart: unless-stopped | ||
| command: /go/bin/collector-linux -cassandra.servers=cassandra -cassandra.keyspace=jaeger_v1_dc1 -cassandra.connections-per-host 2 | ||
| jaeger-agent: | ||
| image: jaegertracing/jaeger-agent:0.5 | ||
| networks: | ||
| - jaeger | ||
| ports: | ||
| - "5775:5775/udp" | ||
| - "5778:5778" | ||
| - "6831:6831/udp" | ||
| - "6832:6832/udp" | ||
| depends_on: | ||
| - cassandra-scheme | ||
| restart: unless-stopped | ||
| command: /go/bin/agent-linux -collector.host-port=jaeger-collector:14267 | ||
| jaeger-query: | ||
| image: jaegertracing/jaeger-query:0.5 | ||
| networks: | ||
|
There was a problem hiding this comment. yep, you need to name the network even if its configuration is basically an empty object. you could configure some stuff here, but we don't need anything beside the defaults. So we are just creating the network with the name we are using above. There was a problem hiding this comment. you probably noticed my comment is intended to be for line 69 :) The correct answer for this line is: the query joins the network to reach the cassandra db as it will inject the name resolving for |
||
| - jaeger | ||
| ports: | ||
| - "16686:16686" | ||
| depends_on: | ||
| - cassandra-scheme | ||
| restart: unless-stopped | ||
| command: /go/bin/query-linux -cassandra.servers=cassandra -cassandra.keyspace=jaeger_v1_dc1 --query.static-files=/go/jaeger-ui/ | ||
| networks: | ||
| jaeger: #defaultnetwork | ||
| volumes: | ||
| cassandra-data: {} | ||
| cassandra-logs: {} | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
given that "compose" is unlikely to be used for production, perhaps
latestimage would be better here?@pavolloffay but even with
latestI don't think this can be used as a base for crossdock test since the crossdock should build the images from the current source code.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.
I could simply override image configuration https://docs.docker.com/compose/extends/#adding-and-overriding-configuration.
Or crossdock target could compile images, and run the compose.
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.
think it could be altered to do a live build, https://docs.docker.com/compose/compose-file/compose-file-v2/#build for the image on the test infrastructure, but i'm not 100% aware of all build prerequisites for the jaeger components to build. For the purpose of handing it over to people who are interested in trying out the setup with all components (not the standalone way), i'd rather vote for fixed versions, but that would indeed be followed by regular updates. Given the test run properly, than "latest" wouldn't be an issue. But that's a bit out of scope for me. So probably two docker files? Or even more? There is a stack up and coming with ES, and most likely you won't have the agent on the collectors Infrastructure neither. So probably the jagertracing org would indeed be a better fit.
For production environments i'll soon setup a rancher catalog and add it to the rancher repo anyways.