podman issue with service return code?

[Jibec]

I am using podman on a Fedora server.
Since the beginning of using Woodpecker with Podman, I see container errors. I assume this is related to a lack of full support of podman #85 (which is fine)

I'm using a database for CI tests:

services:
  - name: postgres
    image: private.repo/translation-storage-postgresdb-test:latest
    pull: true

this service fails with the response: "Error response from daemon: no such container"

The impact: the worflow is identified as failed, while it does what is expected.

here are more logs:

1788466322368	2026-09-03T20:12:02.368Z	{"level":"error","error":"could not stop container 'clone': Error response from daemon: no container with name or ID \"wp_01M1MECMRF8N468DJZD68Z5P0B\" found: no such container\ncould not kill container 'clone': Error response from daemon: no container with name or ID \"wp_01M1MECMRF8N468DJZD68Z5P0B\" found: no such container","time":"2026-09-03T20:12:02Z","message":"could not destroy all containers"}

1788466470400	2026-09-03T20:14:30.400Z	{"level":"error","error":"could not stop container 'formatting controls': Error response from daemon: no container with name or ID \"wp_01M1MECN0BR0YZKAEK7KSF1MW8\" found: no such container\ncould not kill container 'formatting controls': Error response from daemon: no container with name or ID \"wp_01M1MECN0BR0YZKAEK7KSF1MW8\" found: no such container","time":"2026-09-03T20:14:30Z","message":"could not destroy all containers"}

1788466898295	2026-09-03T20:21:38.295Z	{"level":"error","error":"could not stop container 'clone': Error response from daemon: no container with name or ID \"wp_01M1MEY6YJWD9MMCKTS7WTD0FN\" found: no such container\ncould not kill container 'clone': Error response from daemon: no container with name or ID \"wp_01M1MEY6YJWD9MMCKTS7WTD0FN\" found: no such container","time":"2026-09-03T20:21:38Z","message":"could not destroy all containers"}

1788483616351	2026-09-04T01:00:16.351Z	{"level":"error","error":"could not stop container 'clone': Error response from daemon: no container with name or ID \"wp_01M1MYWDGX6Q7NCXGBZ4HQ5QVT\" found: no such container\ncould not kill container 'clone': Error response from daemon: no container with name or ID \"wp_01M1MYWDGX6Q7NCXGBZ4HQ5QVT\" found: no such container","time":"2026-09-04T01:00:16Z","message":"could not destroy all containers"}

1788506457150	2026-09-04T07:20:57.150Z	{"level":"error","error":"could not stop container 'clone': Error response from daemon: no container with name or ID \"wp_01M1NMNF1MV6A466RF8YMBF0KP\" found: no such container\ncould not kill container 'clone': Error response from daemon: no container with name or ID \"wp_01M1NMNF1MV6A466RF8YMBF0KP\" found: no such container","time":"2026-09-04T07:20:57Z","message":"could not destroy all containers"}

1788506457255	2026-09-04T07:20:57.255Z	{"level":"error","error":"could not stop container 'clone': Error response from daemon: no container with name or ID \"wp_01M1NMNF0RJPP8M68EV17YN0ED\" found: no such container\ncould not kill container 'clone': Error response from daemon: no container with name or ID \"wp_01M1NMNF0RJPP8M68EV17YN0ED\" found: no such container","time":"2026-09-04T07:20:57Z","message":"could not destroy all containers"}

1788529965207	2026-09-04T13:52:45.207Z	{"level":"error","error":"could not stop container 'clone': Error response from daemon: no container with name or ID \"wp_01M1PB2BS51QCKWQ94M2W725TV\" found: no such container\ncould not kill container 'clone': Error response from daemon: no container with name or ID \"wp_01M1PB2BS51QCKWQ94M2W725TV\" found: no such container","time":"2026-09-04T13:52:45Z","message":"could not destroy all containers"}

1788529965459	2026-09-04T13:52:45.459Z	{"level":"error","workflow_id":"228","repo":"interne/translation-storage","pipeline_number":"36","error":"Error response from daemon: no such container","step":"database","time":"2026-09-04T13:52:45Z","message":"detached step failed while running"}

1788529965483	2026-09-04T13:52:45.483Z	{"level":"error","workflow_id":"229","repo":"interne/translation-storage","pipeline_number":"37","error":"uuid=01M1PB2C38RJBC9TNQMX1Z4Q3W: exit code 2","step":"database","time":"2026-09-04T13:52:45Z","message":"detached step failed while running"}

1788529965499	2026-09-04T13:52:45.499Z	{"level":"error","workflow_id":"228","repo":"interne/translation-storage","pipeline_number":"36","error":"Error response from daemon: no such container","step":"database","time":"2026-09-04T13:52:45Z","message":"failed to trace detached step result"}

1788529965521	2026-09-04T13:52:45.521Z	{"level":"error","workflow_id":"229","repo":"interne/translation-storage","pipeline_number":"37","error":"uuid=01M1PB2C38RJBC9TNQMX1Z4Q3W: exit code 2","step":"database","time":"2026-09-04T13:52:45Z","message":"failed to trace detached step result"}

1788530162849	2026-09-04T13:56:02.849Z	{"level":"error","error":"could not stop container 'database': Error response from daemon: no container with name or ID \"wp_01M1PB2C38RJBC9TNQMX1Z4Q3W\" found: no such container\ncould not kill container 'database': Error response from daemon: no container with name or ID \"wp_01M1PB2C38RJBC9TNQMX1Z4Q3W\" found: no such container","time":"2026-09-04T13:56:02Z","message":"could not destroy all containers"}

1788530180034	2026-09-04T13:56:20.034Z	{"level":"error","error":"could not stop container 'clone': Error response from daemon: no container with name or ID \"wp_01M1PB8XTCQN46DGBHFYC0VEJV\" found: no such container\ncould not kill container 'clone': Error response from daemon: no container with name or ID \"wp_01M1PB8XTCQN46DGBHFYC0VEJV\" found: no such container","time":"2026-09-04T13:56:20Z","message":"could not destroy all containers"}

1788530180295	2026-09-04T13:56:20.295Z	{"level":"error","repo":"interne/translation-storage","pipeline_number":"38","workflow_id":"230","error":"Error response from daemon: no such container","step":"database","time":"2026-09-04T13:56:20Z","message":"detached step failed while running"}

1788530180325	2026-09-04T13:56:20.325Z	{"level":"error","pipeline_number":"39","workflow_id":"231","repo":"interne/translation-storage","error":"uuid=01M1PB8Y1D26S7MCHK4MBNXA2Y: exit code 2","step":"database","time":"2026-09-04T13:56:20Z","message":"detached step failed while running"}

1788530180396	2026-09-04T13:56:20.396Z	{"level":"error","repo":"interne/translation-storage","pipeline_number":"38","workflow_id":"230","error":"Error response from daemon: no such container","step":"database","time":"2026-09-04T13:56:20Z","message":"failed to trace detached step result"}

1788530180400	2026-09-04T13:56:20.400Z	{"level":"error","pipeline_number":"39","workflow_id":"231","repo":"interne/translation-storage","error":"uuid=01M1PB8Y1D26S7MCHK4MBNXA2Y: exit code 2","step":"database","time":"2026-09-04T13:56:20Z","message":"failed to trace detached step result"}

1788530372840	2026-09-04T13:59:32.840Z	{"level":"error","error":"could not stop container 'clone': Error response from daemon: no container with name or ID \"wp_01M1PB8Y1D26S7MCHK4HPZCH81\" found: no such container\ncould not kill container 'clone': Error response from daemon: no container with name or ID \"wp_01M1PB8Y1D26S7MCHK4HPZCH81\" found: no such container","time":"2026-09-04T13:59:32Z","message":"could not destroy all containers"}

1788530815709	2026-09-04T14:06:55.709Z	{"level":"error","error":"could not stop container 'clone': Error response from daemon: no container with name or ID \"wp_01M1PBWT06WZ5ZWEHPFR3CH3VS\" found: no such container\ncould not kill container 'clone': Error response from daemon: no container with name or ID \"wp_01M1PBWT06WZ5ZWEHPFR3CH3VS\" found: no such container","time":"2026-09-04T14:06:55Z","message":"could not destroy all containers"}

1788530815728	2026-09-04T14:06:55.728Z	{"level":"error","error":"could not stop container 'build and test': Error response from daemon: no container with name or ID \"wp_01M1PBWTA0FGPKF4GZ6NWXQ012\" found: no such container\ncould not kill container 'build and test': Error response from daemon: no container with name or ID \"wp_01M1PBWTA0FGPKF4GZ6NWXQ012\" found: no such container","time":"2026-09-04T14:06:55Z","message":"could not destroy all containers"}

1788531268295	2026-09-04T14:14:28.295Z	{"level":"error","error":"could not stop container 'create postgres container for ci': Error response from daemon: no container with name or ID \"wp_01M1PCAH903VXMRTR4RMYM76NW\" found: no such container\ncould not kill container 'create postgres container for ci': Error response from daemon: no container with name or ID \"wp_01M1PCAH903VXMRTR4RMYM76NW\" found: no such container","time":"2026-09-04T14:14:28Z","message":"could not destroy all containers"}

1788531274766	2026-09-04T14:14:34.766Z	{"level":"error","error":"could not stop container 'postgres': Error response from daemon: no container with name or ID \"wp_01M1PCAGXCV8E6KZCETYWHW8VX\" found: no such container\ncould not kill container 'postgres': Error response from daemon: no container with name or ID \"wp_01M1PCAGXCV8E6KZCETYWHW8VX\" found: no such container","time":"2026-09-04T14:14:34Z","message":"could not destroy all containers"}

1788531352150	2026-09-04T14:15:52.150Z	{"level":"error","error":"could not stop container 'postgres': Error response from daemon: no container with name or ID \"wp_01M1PCD549RPKZBS35PZAF1CXJ\" found: no such container\ncould not kill container 'postgres': Error response from daemon: no container with name or ID \"wp_01M1PCD549RPKZBS35PZAF1CXJ\" found: no such container","time":"2026-09-04T14:15:52Z","message":"could not destroy all containers"}

1788531371626	2026-09-04T14:16:11.626Z	{"level":"error","error":"could not stop container 'create postgres container for ci': Error response from daemon: no container with name or ID \"wp_01M1PCDQEDH4V7T8D3VX939H35\" found: no such container\ncould not kill container 'create postgres container for ci': Error response from daemon: no container with name or ID \"wp_01M1PCDQEDH4V7T8D3VX939H35\" found: no such container","time":"2026-09-04T14:16:11Z","message":"could not destroy all containers"}
```.


Do I have a way to solve this error or to bypass the issue?
Thanks a lot for your help!

[Jibec]

If I try this, I get the same error message on the step

  - name: postgres
    image: private.repo/ranslation-storage-postgresdb-test:latest
    pull: true
    detach: true
    depends_on:
      - name: create postgres container for ci
        optional: true

anything I could do to bypass this error?

[Jibec]

Adding failure: ignore on the step does the job. The step will remain in failure, but the workflow will be a success anyway.
New code is

  - name: postgres
    image: private.repo/ranslation-storage-postgresdb-test:latest
    pull: true
    detach: true
    depends_on:
      - name: create postgres container for ci
        optional: true

I am closing this discussion since my goal is achieved, but I would love to know if a method exists to prevent those container deletion failures.