


Time="T05:01:40-04:00" level=error msg="Error deleting network: neither iptables nor ip6tables usable" Time="T05:01:40-04:00" level=error msg="error loading cached network config: network \"podman\" not found in CNI cache" configure container to start with `-restart always` Version-Release number of selected component (if applicable):ġ.

If i restart the container manually later there are no problems Overlay 23G 18G 4.If i restart the podman host, the container will refuse to restart while spewing errors. Stopping and restarting docker does not help, and the logging limit in the compose file appears to work for the volumes outside docker, but it does not stop the growth within the container? Is there a way to rm or archive within the container? Is there any way to set a limit and over write ? Please may I ask how to prune NXfilter when running it as a docker compose instance ? My compose file is as below and works well, however the docker container continues to grow and and is fast approaching exhausting disc capacity as an ever growing Overlay file.
