Skip to content

GIP-RECIA/docker-mariadb

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

14 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Docker mariadb for ESCO use

Container docker MariaDB + phpMyAdmin

It provides an easy to use of the mariadb database with a configuration close to production. (in strict mode only expect if an evolution come) But don't use it in production, the mariadb root user doesn't has restriction access (permission are setted on 'root'@'%') !

Requirements

Docker and docker-compose are used to setup the technical environment containing all requirements.

For linux install : see documentation Docker and Docker-compose

Setting up the environment

  • Clone the github repository
git clone git@github.com:GIP-RECIA/docker-mariadb.git
  • Download required docker images
docker-compose pull
  • Build custom docker images
docker-compose build
  • Start containers
docker-compose up -d
  • Shutdown the environment
docker-compose down

or

docker-compose down -v  # All data will be lost !

also is working

docker-compose stop

Services

  • MariaDB should be accessible with mysql command :

     mysql -h 127.0.0.1 -u root -proot

    or by docker native network :

     mysql -h 127.17.0.1 -u root -proot
  • PhpMyAdmin should be accessible from browser url : http://127.0.0.1:8181/ or by docker native ip : http://127.17.0.1:8181/

Check to make

After running first time docker-compose up -d you should check :

  • if all services are accessible
  • on mysql you should have all databases intiated (3 native mariadb database) and with the test database initialized from the default script provided in .docker/mariadb-strict/dump/