[](https://microbadger.com/images/linuxserver/tester "Get your own version badge on microbadger.com")
This internal tool is used as a desktop sandbox in our CI process to grab a screenshot of a hopefully functional endpoint
## Supported Architectures
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
Simply pulling `linuxserver/tester` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | latest |
## Usage
Here are some example snippets to help you get started creating a container from this image.
### docker
```
docker create \
--name=tester \
-e URL=http://google.com \
-p 3000:3000 \
--restart unless-stopped \
linuxserver/tester
```
### docker-compose
Compatible with docker-compose v2 schemas.
```yaml
---
version: "2.1"
services:
tester:
image: linuxserver/tester
container_name: tester
environment:
- URL=http://google.com
ports:
- 3000:3000
restart: unless-stopped
```
## Parameters
Docker images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate `<external>:<internal>` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.
### Ports (`-p`)
| Parameter | Function |
| :----: | --- |
| `3000` | WebUI |
### Environment Variables (`-e`)
| Env | Function |
| :----: | --- |
| `URL=http://google.com` | Specify an endpoint, the container will automatically determine the correct protocol and program to use |
## Environment variables from files (Docker secrets)
You can set any environment variable from a file by using a special prepend `FILE__`.
As an example:
```
-e FILE__PASSWORD=/run/secrets/mysecretpassword
```
Will set the environment variable `PASSWORD` based on the contents of the `/run/secrets/mysecretpassword` file.
## Umask for running applications
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional `-e UMASK=022` setting.
Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up [here](https://en.wikipedia.org/wiki/Umask) before asking for support.
[](https://mods.linuxserver.io/?mod=tester "view available mods for this container.")
We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to enable additional functionality within the containers. The list of Mods available for this image (if any) can be accessed via the dynamic badge above.
## Support Info
* Shell access whilst the container is running:
*`docker exec -it tester /bin/bash`
* To monitor the logs of the container in realtime:
*`docker logs -f tester`
* Container version number
*`docker inspect -f '{{ index .Config.Labels "build_version" }}' tester`
* Image version number
*`docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/tester`
