How can we enable persistence for container resources? | Dagger | Page 1

I am building a Dagger module for LocalStack. In LocalStack, we can persist local resources by setting a flag called PERSISTENCE=1. This is stored into /var/lib/localstack/state, and separated into api_states (LocalStack internal state), and assets (one directory per service). I can set the config variable when starting LocalStack with Dagger, but if I stop it and start it again, the resources are not available. This is an expected behavior since LocalStack runs ephemerally but is there any mechanism on Dagger's end that we can persist the /var/lib/localstack/state and reuse it if the user has set the flag?

#How can we enable persistence for container resources?