
g.raphaelli.com/posts/2015-11-13-docker-data-container-snapshots
Preview meta tags from the g.raphaelli.com website.
Linked Hostnames
4Search Engine Appearance
https://g.raphaelli.com/posts/2015-11-13-docker-data-container-snapshots
Docker Data Container Snapshots
The HTML5 Herald
Bing
Docker Data Container Snapshots
https://g.raphaelli.com/posts/2015-11-13-docker-data-container-snapshots
The HTML5 Herald
DuckDuckGo
https://g.raphaelli.com/posts/2015-11-13-docker-data-container-snapshots
Docker Data Container Snapshots
The HTML5 Herald
General Meta Tags
9- titleDocker Data Container Snapshots - g.raphaelli.com
- charsetutf-8
- viewportwidth=device-width,initial-scale=1
- descriptionThe HTML5 Herald
- author
Open Graph Meta Tags
6- og:urlhttp://g.raphaelli.com/posts/2015-11-13-docker-data-container-snapshots/
- og:site_nameg.raphaelli.com
- og:titleDocker Data Container Snapshots
- og:descriptionIt’s straightforward to create a data container with pre-baked archives included: COPY them on during docker build and off you go. But what if you can’t or don’t want to create the data ahead of time? At RealScout, we recently started experimenting with the approach detailed below to create docker images from postgres snapshots for distribution to development environments. Briefly, it looks like: Create and initialize a data container Start postgres using the volume from that data container Restore data Stop postgres Create an image from the populated data container Setup First, build a data container image, for example with this Dockerfile. : FROM debian:jessie ENV PGDATA /var/lib/postgresql/data # ids must match postgres container RUN groupadd -r -g 999 postgres && useradd -u 999 -r -g postgres postgres RUN mkdir -p -m 0700 ${PGDATA} && chown -R postgres:postgres ${PGDATA} VOLUME ${PGDATA} CMD /bin/true
og:locale
en_us
Twitter Meta Tags
3- twitter:cardsummary
- twitter:titleDocker Data Container Snapshots
- twitter:descriptionIt’s straightforward to create a data container with pre-baked archives included: COPY them on during docker build and off you go. But what if you can’t or don’t want to create the data ahead of time? At RealScout, we recently started experimenting with the approach detailed below to create docker images from postgres snapshots for distribution to development environments. Briefly, it looks like: Create and initialize a data container Start postgres using the volume from that data container Restore data Stop postgres Create an image from the populated data container Setup First, build a data container image, for example with this Dockerfile. : FROM debian:jessie ENV PGDATA /var/lib/postgresql/data # ids must match postgres container RUN groupadd -r -g 999 postgres && useradd -u 999 -r -g postgres postgres RUN mkdir -p -m 0700 ${PGDATA} && chown -R postgres:postgres ${PGDATA} VOLUME ${PGDATA} CMD /bin/true
Link Tags
4- stylesheet/css/normalize.min.css
- stylesheethttp://g.raphaelli.com/fontawesome/css/all.min.css
- stylesheethttps://fonts.googleapis.com/css?family=Roboto+Slab|Ruda
- stylesheet/css/styles.css
Links
10- http://g.raphaelli.com/about
- http://g.raphaelli.com/index.xml
- http://g.raphaelli.com/posts/2015-11-13-docker-data-container-snapshots
- http://g.raphaelli.com/posts/2015-11-20-docker-s3-private-registry
- http://jpetazzo.github.io/2015/09/03/do-not-use-docker-in-docker-for-ci