Bug: Dockge's compose editor strips the leading zero from tmpfs mode

⚠️ Please verify that this bug has NOT been reported before.

• I checked and didn't find similar issue

️ Security Policy

• I agree to have read this project Security Policy

Description

tmpfs.mode is an octal permission value. In YAML, the leading 0 on an unquoted number is what tells the parser to resolve the scalar as octal. Dropping it (or quoting the value as a string which is equally wrong) changes how the number gets interpreted and can silently produce a different or invalid mode.

References:

• Compose file reference — tmpfs.mode
• YAML 1.1 tag:yaml.org,2002:int spec — leading zero signals octal
• compose-go types — ServiceVolumeTmpfs.Mode is uint32
• compose-spec JSON schema — tmpfs mode field

Reproduction steps

Compose file contains:

      - type: tmpfs
        target: /app/cache/highlight
        tmpfs:
          mode: 01777

Edit and save the file via Dockge's editor (no manual changes to this line). Result:

- type: tmpfs
        target: /app/cache/highlight
        tmpfs:
          mode: 1777

Expected behavior

Dockge's save/edit path should not modify numeric literals it isn't asked to change — 01777 should round-trip as 01777, not 1777.

Actual Behavior

Untouched numeric literals that weren't touched in the edit.

Dockge Version

1.5.0

Operating System and Arch

image: louislam/dockge:1 on Archlinux 7.1.4-arch1-1

Browser

Vivaldi 8.1.4087.58 (Official Build) (64-bit)

Docker Version

docker 1:29.6.2-1

NodeJS Version

n/a

Relevant log output