Incorporating a spack.lock file into containerize workflow?

[George Hartzell]

One of the attractive bits of environments is being able to create a
spack.lock file that can be used to ensure repeatable builds across
time and/or sites.

Is there a way to feed that in to the `spack containerize` process?
It parses its input `spack.yaml` and generates a new one inside the
container, does that invalidate the idea?

I'd like to be able to build the same set of things in both
containerized and non-containerized environments.

Thanks,

g.