[Support]: Errno 21 Is a directory
See original GitHub issueDescribe the problem you are having
Complete and total newbie here, but I’ve made it this far.
Whenever I run docker-compose up I get:
"Errno 21 Is a Directory: ‘/config/config.yml’
My docker-compose.yml is located at Users/me/Frigate and my config.yml is located at Users/me/Frigate/config. The paths are written as such in the docker-compose.yml file (don’t have access to those files at the moment but can post them later).
I’ve read the threads here with the Errno 21 issue and didn’t get anywhere. It’s a file, not a Directory! I don’t know what I’m doing wrong.
Any suggestions?
Version
Amd64
Frigate config file
Can post later.
Relevant log output
-
FFprobe output from your camera
-
Frigate stats
No response
Operating system
Other
Install method
Docker Compose
Coral version
CPU (no coral)
Network connection
Wireless
Camera make and model
Reolink
Any other information that may be helpful
Ubuntu
Issue Analytics
- State:
- Created 2 years ago
- Comments:25 (2 by maintainers)
Top Results From Across the Web
"IsADirectoryError: [Errno 21] Is a directory: " It is a file
It treats files and directories separately, and can recurse inside the subdirectories to find more files in a iterative way:
Read more >IsADirectoryError: [Errno 21] Is a directory in Python | bobbyhadz
The Python IsADirectoryError: [Errno 21] Is a directory occurs when we try to interact with a directory as if it were a file....
Read more >IsADirectoryError: [Errno 21] Is a directory - PyTorch Forums
The error is raised, since you are passing a path to a directory instead of a model checkpoint. Make sure to pass the...
Read more >[Errno 21] X Is a directory' when removing files in a folder ...
Hi, I'm running a python script which removes any image within the target folder, 'images', that does not have an xml file that...
Read more >[Errno 2] No such file or directory or IsADirectoryError
To get rid of this error you can try using Python file exists methods to check that at least python sees the file...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You need to create the path and file on your host before starting the container. If you don’t, docker will create the path assuming you want a directory. That will cause this error. Clean up the directory created by docker then create a file called config.yml instead according to the docs. Then you can start the container.
It must exist where you’ve told proxmox / the config file that it exists. If that error occurs is 95% of the time means that the mapping is incorrect and the frigate.yml (or whatever it is named in the volume mapping) is not where docker is being told it is.