Bad / incorrect Docker Compose generated

Description

After updating from DragonFish to ElectricEel all apps are not working.

I only get issues like:
Failed 'up' action for 'nginx-proxy-manager' app. Please check /var/log/app_lifecycle.log for more details

app_lifecycle.log:

(ERROR) app_lifecycle.compose_action():56 - Failed 'up' action for 'nginx-proxy-manager' app: 1 error(s) decoding: 'group_add[0]' expected type 'string', got unconvertible type 'int', value: '568' (ERROR) app_lifecycle.compose_action():56 - Failed 'up' action for 'immich' app: configs.permissions_actions_data Additional property content is not allowed

and it happens on ALL containers. even creating new are failing.
/mnt/.ix-apps/app_configs/nginx-proxy-manager/versions/1.1.11/templates/rendered/docker-compose.yaml:



{"services": {"npm": {"cap_add": ["CHOWN", "DAC_OVERRIDE", "FOWNER", "SETGID", "SETUID"], "cap_drop": ["ALL"], "deploy": {"resources": {"limits": {"cpus": "2", "memory": "1024M"}}}, "environment": {"DB_SQLITE_FILE": "/data/database.sqlite", "GID": "568", "GROUP_ID": "568", "NVIDIA_VISIBLE_DEVICES": "void", "PGID": "568", "PUID": "568", "TZ": "Europe/Berlin", "UID": "568", "UMASK": "002", "UMASK_SET": "002", "USER_ID": "568"}, "group_add": [568], "healthcheck": {"interval": "10s", "retries": 30, "start_period": "10s", "test": "/bin/check-health", "timeout": "5s"}, "image": "jc21/nginx-proxy-manager:2.12.3", "platform": "linux/amd64", "ports": [{"mode": "ingress", "protocol": "tcp", "published": 30020, "target": 81}, {"mode": "ingress", "protocol": "tcp", "published": 30021, "target": 80}, {"mode": "ingress", "protocol": "tcp", "published": 30022, "target": 443}], "privileged": false, "restart": "unless-stopped", "security_opt": ["no-new-privileges=true"], "stdin_open": false, "tty": false, "volumes": [{"bind": {"create_host_path": false, "propagation": "rprivate"}, "read_only": false, "source": "/mnt/SSD/nginx", "target": "/data", "type": "bind"}, {"bind": {"create_host_path": false, "propagation": "rprivate"}, "read_only": false, "source": "/mnt/SSD/certificates", "target": "/etc/letsencrypt", "type": "bind"}]}}, "volumes": {}, "x-notes": "# Nginx Proxy Manager\n\n## Default Username and Password\n\nThe First time you log into the Nginx Proxy Manager UI, use the following credentials.\nYou will be prompted to change them on first login.\n\n- Username: `admin@example.com`\n- Password: `changeme`\n\n## Bug Reports and Feature Requests\n\nIf you find a bug in this app or have an idea for a new feature, please file an issue at\nhttps://github.com/truenas/apps\n\n", "x-portals": [{"host": "0.0.0.0", "name": "Web UI", "path": "/", "port": 30020, "scheme": "http"}]}


Is there a way to further get into it?

I have the suspicion that the generation broke.

Problem/Justification

None

Impact

None

Activity

Show:

Bug Clerk March 10, 2025 at 8:36 AM

This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.

SaiCode March 7, 2025 at 9:53 PM

OMG yeah
mv /root/.docker /root/.old_docker
with
systemctl restart docker
fixed it.

Thank You!

( you can close it but might be a nice idea to add that as a troubleshooting step)


Docker Info:

Client: Docker Engine - Community Version: 27.1.1 Context: default Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.16.1 Path: /usr/libexec/docker/cli-plugins/docker-buildx compose: Docker Compose (Docker Inc.) Version: v2.12.2 Path: /root/.docker/cli-plugins/docker-compose Server: Containers: 3 Running: 3 Paused: 0 Stopped: 0 Images: 3 Server Version: 27.1.1 Storage Driver: overlay2 Backing Filesystem: zfs Supports d_type: true Using metacopy: false Native Overlay Diff: true userxattr: false Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 2 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 runc Default Runtime: runc Init Binary: docker-init containerd version: 2bf793ef6dc9a18e00cb12efb64355c2c9d5eb41 runc version: v1.1.13-0-g58aa920 init version: de40ad0 Security Options: apparmor seccomp Profile: builtin cgroupns Kernel Version: 6.6.44-production+truenas Operating System: Debian GNU/Linux 12 (bookworm) OSType: linux Architecture: x86_64 CPUs: 32 Total Memory: 94.21GiB Name: truenas ID: 0c802fca-3b93-4b1d-a0ff-b44a78704489 Docker Root Dir: /mnt/.ix-apps/docker Debug Mode: false Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false Default Address Pools: Base: 172.16.0.0/12, Size: 24

Bug Clerk March 7, 2025 at 8:25 PM

Thank you for submitting this TrueNAS Bug Report! So that we can quickly investigate your issue, please attach a Debug file and any other information related to this issue through our secure and private upload service below. Debug files can be generated in the UI by navigating to System -> Advanced -> Save Debug.

https://ixsystems.atlassian.net/servicedesk/customer/portal/15/group/37/create/153

Stavros March 7, 2025 at 8:23 PM
Edited

I suspect there is some old docker config dir in the root home. Probably from doing something on previous installations.
You can verify with

docker info


If you see under compose the path /root/.docker....
You can run this on TrueNAS Shell.

mv /root/.docker /root/.old_docker

Then try again, it should work fine.

Known Error

Details

Assignee

Reporter

Labels

Time remaining

0m

Components

Fix versions

Priority

Katalon Platform

Created March 7, 2025 at 8:20 PM
Updated March 10, 2025 at 8:36 AM
Resolved March 10, 2025 at 8:36 AM