38 lines
1.5 KiB
Markdown
38 lines
1.5 KiB
Markdown
|
# Serious Business
|
||
|
|
|
||
|
|
Three flags are contained within this challenge. Just name them Serious_Business 1, Serious_Business 2, ...
|
||
|
|
The description can be the same for all of them.
|
||
|
|
|
||
|
|
## Text
|
||
|
|
There's this really important meeting going on in my company right now. Turns out some of my colleagues are taking notes, and they're being streamed in real time! I sure hope that no confidential data gets leaked. Have a look at their notes yourself:
|
||
|
|
|
||
|
|
URL:9001
|
||
|
|
|
||
|
|
URL:9002
|
||
|
|
|
||
|
|
URL:9003
|
||
|
|
|
||
|
|
## Files
|
||
|
|
Nothing.
|
||
|
|
|
||
|
|
## Deployment
|
||
|
|
A docker-compose is provided that should make it easy to deploy these challenges. All deployment details should be in there.
|
||
|
|
A minor edit needs to be done to properly deploy the challenge: they are marked in the docker-compose.
|
||
|
|
`localhost` needs to be changed to the IP address of the server that the challenge will run on.
|
||
|
|
This change needs to happen on 4 different lines.
|
||
|
|
|
||
|
|
The defined services that contain port mappings need to be reachable from the outside.
|
||
|
|
Please don't change the ports, especially the one from the kafka-rest service, that would break everything.
|
||
|
|
Other communication happens though the internal docker network, implicitly created by docker-compose.
|
||
|
|
|
||
|
|
When doing a `docker-compose up`, forcefully recreate the containers, so run:
|
||
|
|
```bash
|
||
|
|
docker-compose up --force-recreate
|
||
|
|
```
|
||
|
|
Otherwise, zookeeper can retain some state regarding kafka broker ids, causing the broker to fail on startup.
|
||
|
|
|
||
|
|
When changing build arguments, all containers will need to be rebuilt. To do so run:
|
||
|
|
```bash
|
||
|
|
docker-compose build
|
||
|
|
```
|