config.json:/var/noisedash/config/default.json -name noisedash noisedash/noisedash:latest We’ll start, as before, with a quick docker run.įirst, I’ll make a couple docker volumes it can docker run -d -p 1432:1432 -v noisedb:/var/noisedash/db -v samples:/var/noisedash/samples -v. Just so you can see the subtle animations, a quick tour: NoisedashĪnother useful tool, that probably could just be an app as well, is Noisedash. While I could externalize this with a Kubernetes externalEndpoint, I think it’s best for just my usage to debug when needed. I should point out there is a dark mode (the little icon on the right of the headings): Now, when I view Logs, I can see how much space is being consumed by logs, which I guess is the goal here - find waste. In the windows WSL instance, I got a blank page on “containers”, however here I see a few, including some that failed to run listed: It complains it lacks access to logs and the mounts seem to struggle with Windows locations While I don’t see space reclaimed in the UI, i do see the absence of the older imagesĪ few things don’t work so well. Untagged: /freshbrewedprivate/myghrunner:1.1.0 WARNING! This will remove all images without at least one container associated to them.Īre you sure you want to continue? y $ docker image prune -a -filter "until=24m" Time="" level=error msg="failed to get the list of containers" err="Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Time="" level=info msg="starting http server at 0.0.0.0:9090" Time="" level=info msg="calculating size of volumes." Time="" level=info msg="docker engine API (1.24)" Status: Downloaded newer image for amerkurev/doku:latest $ docker run -p 9900:9090 -name dokutest amerkurev/doku
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |