Skip to content

adding docker-compose file troubleshooting section #31

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.

Sign up for GitHub

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

Open
halr9000 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

adding docker-compose file troubleshooting section #31

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 16 additions & 1 deletion enterprise/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -239,7 +239,22 @@ The following mount points require special permissions:

Overriding the SPLUNK_USER envrionment variable to an authorized user (such as "root") gives you the required access to the mount points that the Docker app needs to analyze the collected Docker information.

## Troubleshoot upgrade problems with docker-compose
## Docker-compose errors

If `docker-compose up` issues errors, first try running `docker-compose config` to check the contents of your `docker-compose.yml` file. Many issues can be solved by checking the indentation of your source, and referencing the [Compose File Reference](https://docs.docker.com/compose/compose-file/). Some error examples are below:

```
$ docker-compose up
ERROR: The Compose file './docker-compose.yml' is invalid because:
Unsupported config option for services.vsplunk: 'splunk'

$ docker-compose up
ERROR: The Compose file './docker-compose.yml' is invalid because:
Unsupported config option for services.splunk: 'SPLUNK_ENABLE_LISTEN'
services.splunk.environment contains an invalid type, it should be an object, or an array
```

## Upgrade problems with docker-compose

If you use `docker-compose` (or reference an existing volume with `docker run`) to configure and run your Docker image and the Splunk Enterprise Docker container detects an upgrade after you make a change to `docker-compose.yml`, complete the following procedure to make the image ignore the upgrade prompt:

Expand Down