Convington Posted June 25 Share Posted June 25 awhile back my flash drive got whacked and I had to put in a new one and re-install dockers. I'm guessing I did something wrong because my docker.img keeps getting larger. I expanded it to 60GB and it is almost full again. I'm guessing it is SABNZB, but I'm not quite sure what I did wrong with the mapping that could have caused it. I'll paste the applications that are most likely (at least from what I've read): I'm not real good at this stuff, so take it easy on me Quote Link to comment
JonathanM Posted June 25 Share Posted June 25 10 hours ago, Convington said: what I did wrong with the mapping It's not usually the mapping that is the issue, but the settings inside the application not pointing to the mapping. If sab is putting downloads somewhere besides /data, that would do it, also if the 'arrs aren't moving it to /media, that would do it as well. Quote Link to comment
Convington Posted June 25 Author Share Posted June 25 4 minutes ago, JonathanM said: It's not usually the mapping that is the issue, but the settings inside the application not pointing to the mapping. If sab is putting downloads somewhere besides /data, that would do it, also if the 'arrs aren't moving it to /media, that would do it as well. That looks to be set up correctly: And then: Does that seem correct to you? Thanks! Quote Link to comment
JonathanM Posted June 25 Share Posted June 25 1 minute ago, Convington said: Does that seem correct to you? Yep. At the bottom of the Docker tab, click the Container Size button and see what it says. Quote Link to comment
Convington Posted June 25 Author Share Posted June 25 Wow - I totally missed that button That is informative: Looks like logging is taking up most of the data on mostly on NodeRed. Quote Link to comment
Convington Posted June 25 Author Share Posted June 25 I do not know why this is not conforming to the settings here: I have not changed this setting, so I can only assume it was set like this before I installed any of the dockers listed. Quote Link to comment
Convington Posted June 25 Author Share Posted June 25 I just did a truncate of all the logs in the docker system, so I think I'm in better shape now: I ran a truncate on all the *-json.log files within /var/lib/docker/containers. After I looked here I then restarted Docker. Doesn't really look like it gained any space, though: I get the bottom part, but it looks like 52GB of the 60GB used from the top section. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.