My guess (been there, done that):
you did not provide the correct location for your containers nor the correct location for the config files.
Some (or all ?) of it came together in one big place.
Show your config, please.
The container configurations are as follows:
/container mounts
add dst=/root/.config/aaa name=aaa_config src=/usb1/docker/volumes/aaa
add dst=/root name=bbb_config src=/usb1/docker/volumes/bbb
add dst=/data name=ccc_config src=/usb1/docker/volumes/ccc
/container
add entrypoint="sh /root/.config/aaa/start.sh" interface=veth2 mounts=aaa_config root-dir=/usb1/docker/rootdir/aaa start-on-boot=yes
add interface=veth3 mounts=bbb_config root-dir=/usb1/docker/rootdir/bbb start-on-boot=yes workdir=/app
add interface=veth4 mounts=ccc_config root-dir=/usb1/docker/rootdir/ccc start-on-boot=yes
/container config
set layer-dir=usb1/docker/overlayfs registry-url=https://registry-1.docker.io tmpdir=usb1/docker/pull
each of the three containers is allocated its own root directory and mounted folder. When the "aaa" container is eventually deleted, all files in its mounted directory /usb1/docker/volumes/aaa are lost, and a residual ".rm.aaa" folder appears in its root directory folder.
Another issue is that the "ccc" container cannot be directly deleted; it seems that all three containers need to be deleted in sequence, otherwise, the phenomenon described in the topic occurs, causing mutual interference.
Could you please assist in analyzing this matter? Thank you.