Issues with putting dockerized Postgres OLTP database in read only

I have a dockerized postgres 9.3.5 OLTP instance that I’m going to update to 9.5.2. Instead of shutting it down and doing a pg_dumpal to a file and then load it I would like to spin up a new docker container and pipe the database pg_dumpall -h localhost -p [port] -U postgres | psql -h localhost -U postgres -p [port]. I’m thinking I could alter the postgresql.conf to be in read only mode. This would temporarily mess with my app but at least users could still SELECT. Is there a better way to go about this? Are there any big issues with putting in read only mode while I pipe the database over?

  • Can't mount Windows host directory to Docker container
  • Can I ask for RAM of container exceed the physical memory on the single host with Docker-Swarm
  • InnoDB error on mariadb oficial docker image
  • Why orientDB connection to localhost of docker is refused
  • How to set volume for dokku-persistent-storage
  • Windows Docker in Linux machine
  • Difference between docker-compose and manual commands
  • Docker Push Fails
  • FTP does not work from mesos docker container
  • Cannot access Django webpage when using Docker to run a virtualized Django project on Linux server
  • How to run an application as 100 services with docker? [closed]
  • How to create a superuser in Django with Linux shell script?
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.