Johan's answer is a good one.
In terms of packaging, the usual options apply for packaging tools (Zip, Tar, Bagit etc.). However, the Open Geospatial Consortium recently finalized the GeoPackage Encoding Standard. The GeoPackage Encoding Standard (http://www.opengeospatial.org/standards/geopackage)
“defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a "native" storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth.”
It’s not quite the same as a container wrapper. It’s an SQLite database schema. As they say (http://www.geopackage.org/):
“Install Spatialite – the premiere spatial extention to SQLite – and you get all the performance of a spatial database along with the convenience of a file-based data set that can be emailed, shared on a USB drive or burned to a DVD.”
It is being implemented in a variety of tools, but I’d need more information to determine its suitability as a preservation packaging format for geospatial data.