Now I have sound in both firefox and seamonkey within this container. Don't know yet how to configure it in the seamonkey container. Maybe try editing the container config file.
I like to create a sakura (terminal) container, as that way the container is like a separate system that you can log into at the command level and run commands etc.
For firefox for instance, after having created a sakura container I run it so that its activated, and then download the
firefox...bz2 using the main (non container) seamonkey, and then use the main system to copy that file into the container and then extract it (I use /usr/lib as the location to extract to, so I end up with a /usr/lib/firefox folder with the firefox binary inside that folder). I also copy across the three libpulse type files that
Oscar's apulse (64 bit apulse-0.1.11-x86_64.pet) pet installs (I install it to the main system using pet, and copy the /usr/lib/libpul... files to the containers /usr/lib folder).
That (terminal container) way you can also run other things such as sound configuring ...etc. within the container.
Will have to come back and edit the path as not in Easy at present, something like /mnt/wkg/containers/sakura/.session is the root folder, so /usr/lib within that would be /mnt/wkg/containers/sakura/.session/usr/lib To repeat however the container must be running, otherwise that folder is just empty.
The other way for a container such as seamonkey might be to edit the ec-chroot file in that containers / folder (/mnt/wkg/containers/sakura/container ??? (again I'll have to check that path)) so that it just ran sakura instead of seamonkey. Hard code EXE=sakura variable for instance and then close that container session and restart it again so it ran sakura instead of seamonkey ... so you could edit things, and then after having made edits revert back again to running seamonkey.
The other route might be via /mnt/sdd2/containers/ and then the particular container such as sakura folder. I think that is where the current rw overlay files are stored.