Modify Docker logging under DSM 7.0

Currently reading
Modify Docker logging under DSM 7.0

Dear Docker experts,

I am running HomeAssistant under Docker on DSM 7.0. To avoid frequent HDD access, I want to disable docker logging. But how to do so?

I modified:

/var/packages/Docker/etc/dockerd.json

to

"log-driver" : "none"

and the

containers's json config file uploaded to the Docker GUI
(/var/packages/Docker/etc/CONTANER_NAME.config)

adding

"log-driver": "none",

but to no effect. Docker still stubbornly writes every five minutes or so into containerID/log.db.

Please help

Best,

Stefan
 
Solution
Solved.
Thank you fredbert!

Documentation:

Place files docker-compose.yml and resolv.conf (see below) e.g. into /volume1/docker/homeassistant

Then via Terminal:

$ cd /volume1/docker/homeassistant
$ sudo -i
# docker-compose up -d



docker-compose.yml:

version: "3.9"

services:
home_assistant:
container_name: homeassistant
restart: always
image: homeassistant/home-assistant:latest
volumes:
- /tmp/homeassistant/config:/config
environment:
- TZ=Europe/London
network_mode: host
logging:
driver: none

resolv.comf

nameserver 192.168.178.1
nameserver 8.8.8.8
domain fritz.box
Solved.
Thank you fredbert!

Documentation:

Place files docker-compose.yml and resolv.conf (see below) e.g. into /volume1/docker/homeassistant

Then via Terminal:

$ cd /volume1/docker/homeassistant
$ sudo -i
# docker-compose up -d



docker-compose.yml:

version: "3.9"

services:
home_assistant:
container_name: homeassistant
restart: always
image: homeassistant/home-assistant:latest
volumes:
- /tmp/homeassistant/config:/config
environment:
- TZ=Europe/London
network_mode: host
logging:
driver: none

resolv.comf

nameserver 192.168.178.1
nameserver 8.8.8.8
domain fritz.box
 
Upvote 0
Solution

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Old thread notice: There have been no replies in this thread for quite some time. The last reply was on .
The content in this thread may no longer be relevant. It might be better to open a new thread instead.

Similar threads

Good to hear. Deluge has not been updated for almost two years now as an app, nevertheless. But it gives...
Replies
12
Views
713
  • Question
Open an issue on that GitHub page. The developers will be glad to assist. OP has posted two threads on...
Replies
5
Views
845
I'm happy with email notifications but in v0.3.3 of dockcheck the author added apprise notifications...
Replies
4
Views
830
I am also trying to setup a Z-wave USB dongle and am getting stuck after following the same steps as...
Replies
1
Views
925
How did you create the Portainer container in first place? As in exact docker run commands or in case...
Replies
7
Views
1,096
Looks like I triggered you somehow with my post: it was not my intention. I have no idea whether bash or...
Replies
4
Views
1,400
Unable to locate what? The resource or that I use /volume1/system/docker/ to holder bind volumes for my...
Replies
4
Views
1,157

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending threads

Back
Top