Skip to content
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.

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

Running Docker image with custom config file #2485

Closed
12 tasks
hartmanshk opened this issue Oct 10, 2023 · 2 comments
Closed
12 tasks

Running Docker image with custom config file #2485

hartmanshk opened this issue Oct 10, 2023 · 2 comments

Comments

@hartmanshk
Copy link

hartmanshk commented Oct 10, 2023

Which version are you using?

v1.1.1

Which operating system are you using?

  • Linux amd64 standard
  • [x ] Linux amd64 Docker
  • Linux arm64 standard
  • Linux arm64 Docker
  • Linux arm7 standard
  • Linux arm7 Docker
  • Linux arm6 standard
  • Linux arm6 Docker
  • Windows amd64 standard
  • Windows amd64 Docker (WSL backend)
  • macOS amd64 standard
  • macOS amd64 Docker
  • Other (please describe)

Describe the issue

I Just tried to run the Dockerimage with a modified mediamtx.yml file but all i get is this error:

´user@system$ docker run --rm -it --network=host -v $PWD/mediamtx.yml:/mediamtx.yml bluenviron/mediamtx´
´ERR: json: unknown field "pathDefaults"´

I also tried to run the image with an untouched version of the config file directly downloaded as raw file from here - same result.

Describe how to replicate the issue

Just copy mediamtx.yml to your local machine and run the same command as shown in the description above

Did you attach the server logs?

no

Did you attach a network dump?

no

@aler9
Copy link
Member

aler9 commented Oct 10, 2023

hello, pathDefaults is a new setting that will be available starting from the next version. In the meantime, please refer to the v1.1.1 README and sample configuration file:
https://github.com/bluenviron/mediamtx/tree/v1.1.1

@aler9 aler9 closed this as not planned Won't fix, can't repro, duplicate, stale Oct 10, 2023
Copy link
Contributor

This issue is being locked automatically because it has been closed for more than 6 months.
Please open a new issue in case you encounter a similar problem.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants