René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Cannot deserialize value of type `com.github.dockerjava.api.model.Capability`","articleBody":"**OS**: Ubuntu 22.04.5 LTS\n**Docker version**: 28.1.0\n**Docker Compose version**: v2.34.0\n**Docker-java version**: 3.5.0\n\n🐞 **Issue**\nWhen inspecting a Docker container using the docker-java client, I encounter the following exception:\n\n```\njava.lang.RuntimeException: com.fasterxml.jackson.databind.exc.InvalidFormatException: Cannot deserialize value of type `com.github.dockerjava.api.model.Capability` from String \"CAP_DAC_READ_SEARCH\": not one of the values accepted for Enum class: [ALL, SYS_BOOT, DAC_OVERRIDE, NET_RAW, BLOCK_SUSPEND, FOWNER, IPC_LOCK, IPC_OWNER, SYS_PACCT, NET_BIND_SERVICE, WAKE_ALARM, FSETID, DAC_READ_SEARCH, SYS_CHROOT, AUDIT_READ, SYS_RAWIO, SYS_ADMIN, KILL, MAC_ADMIN, SYS_RESOURCE, CHOWN, PERFMON, SETPCAP, SYS_PTRACE, NET_ADMIN, SETFCAP, SYS_NICE, LINUX_IMMUTABLE, BPF, AUDIT_CONTROL, LEASE, AUDIT_WRITE, SYS_MODULE, MKNOD, SYSLOG, MAC_OVERRIDE, SYS_TIME, SETGID, SETUID, CHECKPOINT_RESTORE, SYS_TTY_CONFIG, NET_BROADCAST]\nThis occurs when deserializing the CapAdd field from InspectContainerResponse.\n```\n\n📄 **Example Code**\n\n```\npublic Object inspectContainer(String containerName) {\n    String containerId = getCurrentIdForContainer(containerName);\n    return dockerClient.inspectContainerCmd(containerId).exec();\n}\n```\n🔍 **Analysis**\nThe deserialization fails because Docker returns capabilities with the CAP_ prefix (e.g., CAP_DAC_READ_SEARCH), but the Capability enum in docker-java omits that prefix (e.g., DAC_READ_SEARCH).\n\nAccording to the Docker capabilities [documentation](https://man7.org/linux/man-pages/man7/capabilities.7.html) and types.go, Docker capabilities are typically listed with the CAP_ prefix.\n\nThe Capability enum here: https://javadoc.io/static/com.github.docker-java/docker-java/3.0.6/index.html?com/github/dockerjava/api/model/Capability.html\n\n...does not align directly with the string values Docker returns.\n\n✅ **Suggested Fix**\nCould the enum Capability be enhanced to:\n\nSupport @JsonCreator to allow aliasing/deserialization of names with the CAP_ prefix?\n\nOr alternatively, normalize the incoming capability strings before deserialization?\n\nThis would improve compatibility when parsing real-world Docker API responses, and prevent failures like the one above.","author":{"url":"https://github.com/rzabson2","@type":"Person","name":"rzabson2"},"datePublished":"2025-04-25T10:51:05.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/2432/docker-java/issues/2432"}