blob: 1b7358da21f17a4e37ae54f54ba4ae4054f748f9 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
|
# Docker Bomb Images : CPU
Simple container used to bomb cpu usage for crash testing. !!! WARNING, starting this container will start flooding your CPU by default for 10sec.
You can find information on this image and how to use it by visiting the [Dockerhub registry](https://github.com/startxfr/docker-images)
| [](https://travis-ci.org/startxfr/docker-images) | [Dockerhub Registry](https://hub.docker.com/r/startx/openshift-bomb-cpu) | [Sources](https://github.com/startxfr/docker-images/Bombs/) | [STARTX Profile](https://github.com/startxfr) |
|-------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------|----------------------------------------------------------------------|-----------------------------------------------|
## Running from dockerhub registry
* with `docker` you can run `docker run -it --name="centos" startx/openshift-bomb-cpu` from any docker host
* with `docker-compose` you can create a docker-compose.yml file with the following content
```
fedora:
image: startx/openshift-bomb-cpu:latest
container_name: "os-ocp-bomb-cpu"
environment:
CONTAINER_TYPE: "bomb"
CONTAINER_SERVICE: "cpu"
CONTAINER_INSTANCE: "os-ocp-bomb-cpu"
```
## Using this image in your own container
You can use this Dockerfile template to start a new personalized container based on this container
```
FROM startx/openshift-bomb-cpu:latest
#... your container specifications
CMD ["/bin/sx"]
```
## Environment variable
| Variable | Type | Mandatory | Description |
|---------------------------|----------|-----------|--------------------------------------------------------------------------|
| CONTAINER_INSTANCE | `string` | `yes` | Container name. Should be uning to get fine grained log and application reporting
| CONTAINER_TYPE | `string` | `no` | Container family (os, service, application. could be enhanced
| CONTAINER_SERVICE | `string` | `no` | Define the type of service or application provided
| HOSTNAME | `auto` | `auto` | Container unique id automatically assigned by docker daemon at startup
| TEST_DURATION | `seconds`| `auto` | Running test duration (defautl = 10sec)
## For advanced users
You you want to use this container and code to build and create locally this container. You can follow theses instructions to setup and working environment.
This section will help you if you want to :
* Get latest version of this container Bombs
* Enhance container content by adding instruction in Dockefile before build step
You must have a working environment with the source code of this repository. Read and follow [how to setup your working environment](https://github.com/startxfr/docker-images#setup-your-working-environment-mandatory) to get a working directory. The following instructions assume you are at the top level of your working directory.
### Build & run a container using `docker`
1. Jump into the container directory with `cd Bombs/cpu`
2. Build the container using `docker build -t bomb-cpu .`
3. Run this container
1. Interactively with `docker run -it bomb-cpu`. If you add a last parameter (like `/bin/bash`) to will run this command instead of the default entrypoint. Usefull to interact with this container (ex: `/bin/bash`, `/bin/ps -a`, `/bin/df -h`,...)
2. As a daemon with `docker run -d bomb-cpu`
### Build & run a container using `docker-compose`
1. Jump into the container directory with `cd Bombs/cpu`
2. Run this container
1. Interactively with `docker-compose up` Startup logs appears and escaping this command stop the container
2. As a daemon with `docker-compose up -d`. Container startup logs can be read using `docker-compose logs`
|
