docker image under unraid started filling up after last release? #15316
Unanswered
simondsmason
asked this question in
Ask A Question
Replies: 3 comments 11 replies
-
|
If the docker image is getting too big that indicates you have a folder that is not properly mapped, the docker image should not change size at all |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Yes, that would be the logical explanation. Yet, I cannot see what is causing this. I now realize that this may have been going on for some time as I only recently turned on the notifications. I ran the fix common problems and it pointed out that I didn't have a notification agent enabled. Yes, you would think that would be the issue. I now realize that this might have been going on for some time. I only recently enabled notifications because the fix common problems pointed out that I didn't have a notification agent enabled. Here are my mappings from the docker container. Anything else I should be looking for? Thanks. 
|
Beta Was this translation helpful? Give feedback.
-
|
Do you have the /tmp/cache bind setup in the extra args? |
Beta Was this translation helpful? Give feedback.
-
|
I am going to guess that this is not setup correctly as I didn't even know what it was until you pointed it out. Learn as you go. So I am guessing I need to setup an additional path with a container path of /tmp. Do I point it inside the container - such as /mnt/user/appdata/frigate12/tmp/? |
Beta Was this translation helpful? Give feedback.
7 replies
-
|
so you already have the tmpfs arg there, so I don't know what would be writing to the docker image |
Beta Was this translation helpful? Give feedback.
-
|
Is there anything I can look at while it is happening to gain some insights into what files are doing? Also I have seen some posts about docker image size issues with apps that are run through a reverse proxy generating large tmp files. I understand this to be files that are being transferred out, such as a backup, so not sure it is relevant here. But thought I would bring it up in case it makes sense here. I am accessing Frigate through a reverse proxy. |
Beta Was this translation helpful? Give feedback.
-
I am going to post in the unraid forum to see if I can some more tips on pinning this down. The only thing I can think to do at this point is watch the /tmp and/or /dev/shm folders when things start to fill up. Is Frigate doing any video processing that involves large files? I have 24 hour recording turned on for my cameras. |
Beta Was this translation helpful? Give feedback.
-
|
no, Frigate only works with small file segments |
Beta Was this translation helpful? Give feedback.
-
|
@NickM-27 OK. I rebuilt my docker images and I am running only Frigate. It is still doing it. I have detailed all of my configuration above and there doesn't appear to be any configured ways in which Frigate could be writing to the docker image in large quantities. So far I can't see any smoking guns in terms of files or directories that are ballooning. I have captured the logs for half an hour before the first warning came on docker size. All I can see is a lot of what I believe are calls coming to service images? I am running several touchscreens with the camera images showing so presume that is the cause of that? Anything else look odd here? Should I up the logger settings and if so which log level should I use? Also, I would be willing to step back through older versions to see if it keeps doing this? I might need some help navigating that if it makes sense? Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
@NickM-27 I have rebuilt the docker image. I stepped back to 0.14.0, I stopped 24 hour recording, I disabled a camera that occasionally threw errors, I removed the Birdseye settings which I don't think I need/use anyway. But my docker image is still filling up:
but Frigate doesn't show anything unusual in storage usage:
Posting on the Unraid forums - all suggestions point to temporary files building up during transcoding, etc. Is there anything I can do to see what is eating up this space in the frigate container? Should I go down to one camera or no cameras to see if it does anything? I am starting to run out of ideas here? Thanks. |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
I don't really have any idea, what size is your docker image? I don't see this at all running Frigate in unraid. |
Beta Was this translation helpful? Give feedback.
-
|
What is the docker run command shown when deploying the frigate container? |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
About a week ago I started to get warnings about the docker image getting too big and filling up. The container size stats show nothing out of the ordinary.
frigate12 1.92 GB 4.38 MB 9.49 MB
I have been able to point the finger at Frigate through process of elimination of shutting down containers and bringing them up one at a time. It takes a few hours for this to happen.
I don't see anything in the logs that points me to anything but happy to post if that is useful? I haven't looked at them when the docker image is filling up as I am usually remote and just restart frigate.
I thought I could step back a version to see if it continues? But I am not really sure how to do that so if this is a reasonable test please advise on how to do that.
startup parameters:
--shm-size=512mb --mount type=tmpfs,target=/tmp/cache,tmpfs-size=1000000000 --restart unless-stopped --runtime=nvidia
config file:
Beta Was this translation helpful? Give feedback.
All reactions