Wonder if anyone can tell me what changed with the API from version 3.1.7 ro 3.2.3?
We use the jenkins docker plugin to allow jenkins to connect to our Linux nodes and spin up podman containers to run builds in.
up till now, everything worked fine. on a new Linux node, we ran an update and it picked up the latest podman version from our RedHat Satellite server. On the older Nodes, this is the version jenkins shows when using the cloud "test connection" button from the cloud/template setup screen.
Version = 3.0.2-dev
on the new node to that has the newer version of podman,
newer version:
Version = 3.2.3
However, Jenkins can no longer spin up the containers.
here is the error jenkins provides when trying to start a container with the newer version.:
Note: Disabled 21 sec ago due to error. Will re-enable in 4 min 38 sec.
Reason: Template provisioning failed.
com.fasterxml.jackson.databind.exc.InvalidFormatException: Cannot deserialize value of type `com.github.dockerjava.api.model.Capability` from String "CHECKPOINT_RESTORE": 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, SYS_RAWIO, SYS_ADMIN, KILL, MAC_ADMIN, SYS_RESOURCE, CHOWN, SETPCAP, SYS_PTRACE, NET_ADMIN, SETFCAP, SYS_NICE, LINUX_IMMUTABLE, AUDIT_CONTROL, LEASE, AUDIT_WRITE, SYS_MODULE, MKNOD, SYSLOG, MAC_OVERRIDE, SYS_TIME, SETGID, SETUID, SYS_TTY_CONFIG, NET_BROADCAST] at [Source: (byte[])
the only thing that changed is the newer version of podman. seems like maybe the API is returning some new information of the formatting of the returned info has changed? any help or insights would be greatly appreciated.
Thanks,
Rusty