me too… even if I don’t know what it is 
Can you check that the autospawn = no line does not start with a ; ?
it start with a ;
must I delete it?
Yes, remove the ;. The ; is the character used to comment out a line so the autospawn parameter was never applied… then reboot and once again ps ..., arecord ... and aplay ....
done. now? another
ps aux | grep pulse
Yup… Pretty much 
pi@raspberrypi:~ $ ps aux | grep pulse
pi 720 0.1 1.1 210424 21668 ? S<sl 17:02 0:00 /usr/bin/pulseaudio --daemonize=no
pi 1832 0.0 0.0 7364 580 pts/0 S+ 17:10 0:00 grep --color=auto pulse
Did you reboot after saving the /etc/pulse/client.conf file?
noooooooooooooooooo… erem…
I reboot and retest, but same result
Try to sudo nano ~/.pulse/client.conf and change the autospawn parameter to no (and remove the ;) if the file exists.
doesn’t exist :s it’s really frustrating this pulseaudio…
Nothing with just nano ~/.pulse/client.conf (no sudo) either ?
same result…
Why don’t you remove it with:
sudo apt remove pulseaudio
But I don’t know whether this will remove other packages you need.
Even better (but I’m repeating myself here): just install a Lite version of Raspberry Pi OS, which will save you a lot of time with debugging these problems 
I agree with what @koan said. Installing a Raspberry OS Lite with docker and running the docker run... command above should work directly…
pi@raspberrypi:~ $ ps aux | grep pulse
pi 1690 0.0 0.0 7364 544 pts/0 S+ 17:24 0:00 grep --color=auto pulse
I understand but I can’t… for now if I do that, I can’t access anymore to my domoticz and, as a disabled, I need a lot of these thing…
If you succeed to disable PulseAudio (event temporarily to test), the aplay and arecord command should work as expected and Rhasspy should be able to capture and playback correctly (don’t forget to select the correct PCMs in Rhasspy’s config).
with my previous post, it works? is there any pulsaudio?
Ah… missed it… So now no more PulseAudio… Do the command to record and play work now?