Hello Everyone while doing backup recently i always get these error warning is it normal or worrysome…and how can i get rid of them
I’d call it both somewhat normal and somewhat worrisome if you care about that file’s backup.
--ignore-advisory-locking (Boolean): Ignore advisory locking When reading files Duplicati can skip files that are marked locked by another application to ensure consistency. This flag can disable the check and perform optimistic reads of locked files. * default value: false
Forum commentary here, with a somewhat misplaced mention in the documentation under this:
thankyou i did add to compose but still same
services:
duplicati:
image: lscr.io/linuxserver/duplicati:latest
container_name: duplicati
environment:
- PUID=0
- PGID=0
- TZ=Asia/Kolkata
- SETTINGS_ENCRYPTION_KEY=xxxxx
- CLI_ARGS= #optional
- DUPLICATI__WEBSERVICE_PASSWORD=xxxxxx
- DOTNET_SYSTEM_IO_DISABLEFILELOCKING:true
volumes:
- ./config:/config
- /:/source
ports:
- 8200:8200
restart: always
I don’t use Docker. Are you familiar with the syntax? FWIW four other posts I see are advising:
DOTNET_SYSTEM_IO_DISABLEFILELOCKING=true
although the Duplicati manual has colon space, and you have just colon. I wonder which work?
2 Likes
Although you’re not using it exactly (missing space after colon), I’m not sure manual is right.
The dash in front (see your LinuxServer example) in environment passes the rest to Docker.
Reportedly the value after the = becomes the value, so don’t put any extra characters there.
Without dash in front, you make a YAML mapping, with colon space between key and value.
Duplicati manual does both (which is unusual), and I see someone saying you can’t do both:
Parsing of key-value build args in docker-compose not working #2661
you’re trying to use a “map” (
key: value) inside a list (starting with-)
is what I’d say about the Duplicati manual. Regardless, here are some other commentaries:
environment in dockerdocs showing map syntax and array syntax.
Collections in YAML spec talking about dash-space Sequence versus colon-space Mapping.
Environment variable assignment in Docker Compose - colon way says they both work, but
Why does the YAML spec mandate a space after the colon? says why the space is required.
I suppose instead of turning colon to equal, you could turn it to colon space to see if it works.
2 Likes
Good catch. I looked at the Docker Compose docs and changed the Duplicati docs to match.
1 Like
i just cant thankyou enough all was needed was a = sorry for my foolishness and thankyou so so much it worked like a charm
2 Likes