Docker

Working on different platform either to update, patch, etc need to be notificate for those people that consume that services, it shouldn’t change if that service it’s internal, you must notificate your teams about it. When you’re into your maintenance window you can use a faster way to broadcast everyone you’re working on it; I use this simple solution when I was working into a Jenkins migration, hence I stop the jenkins service and instead of 500 html error I developed a simple html text exposing it by a nginx container by the root path. ...

For those who have been facing the “Maintenance mode active” after applied a nextcloud upgrade by switching container image version, due a major versioning issue. Even when you issue the occ upgrade into continer you gets hit by something like below: www-data@87401bdd2fa8:~/html$ php /var/www/html/occ upgrade Nextcloud or one of the apps require upgrade - only a limited number of commands are available You may use your browser or the occ upgrade command to do the upgrade Setting log level to debug Exception: Updates between multiple major versions and downgrades are unsupported. Update failed Maintenance mode is kept active Resetting log level Keep a eye on this part: Updates between multiple major versions and downgrades are unsupported. as I was running 25 version I can no jump for above 27, if that’s our case, we can edit the file app/config/config.php edit the version of your nextcloud like below: ...

Below you will see the statement I used to deploy a Wordpress as db mariadb (mysql); I shared it to you, cos I’ve been looking out for a good .yml statement piece, but some of them are older or put other set frontend as nginx, etc. I did a simple and easier deployment statement, so here we have: version: '3.3' services: wordpress: depends_on: - db image: wordpress:latest volumes: - ./html:/var/www/html ports: - "8080:80" restart: always environment: WORDPRESS_DB_HOST: db:3306 WORDPRESS_DB_USER: wordpress WORDPRESS_DB_PASSWORD: password links: - db depends_on: - db db: image: mariadb:10.5.4-focal volumes: - ./db_data:/var/lib/mysql restart: always environment: MYSQL_ROOT_PASSWORD: SECRET MYSQL_DATABASE: wordpress MYSQL_USER: wordpress MYSQL_PASSWORD: password ports: - "3306:3306" You can switch the local mount to volume mount it will depend of you design. ...

Part I Containers are environments that host individual applications using a framework like Docker. Docker Editions: Docker CE ( community edition ) free version Docker EE ( enterprise edition) Paid Versions: Stable, released every 4 months. Edge (beta) released every month. For testing EE, support for one year. Example how to create a container: $docker container run --publish 80:80 --detach --name webhost nginx detach: subcommand is to let run the container and keep use the command prompt name: create a container’s name. ...

Here are the steps I made to set a service into my Fedora server to start/stop my Docker-compose (Wikijs) Why I decided to use a docker-compose into a Linux VM machine? —> for make it more stable, faster,portable, isolated, etc. First I stared using Docker for Windows and it was a little bit unstable and not quite easy to handled, so when I switched to Docker compose into a Fedora VM and in that point it was a huge different(I do not recommend to use Docker in Windows); I use a Vmware hypervisor ( in the office we use it ). ...

This is a little resume of how I’m doing a backup procedure of my wikijs database based in Docker-compose. Below are the systems used in my enviroment: Project: Wikijs 2.0 Beta Platform: Docker-Compose DB: Postgres (9.6.14) Server: Fedora Server 30.x86_64 Workstation: Windows 10 (provided by work) 😬 PSQL basic commands: Here are 4 basic commands I use to connect into my Postgre DB and check out DB list and quite. $psql -h localhost -p 5416 -U <my-user> -d <my-database> ...

The following instruction is a solution when you got an error response with live-restore using Docker Swarm in Fedora 28 or highter $ docker swarm init Error response from daemon: --live-restore daemon configuration is incompatible with swarm mode That’s not possible to enable Live-restore and Swarm-mode together. First make sure that the SElinux is Permissive or Disabled. $ sestatus SELinux status: enabled SELinuxfs mount: /sys/fs/selinux SELinux root directory: /etc/selinux Loaded policy name: targeted Current mode: permissive Mode from config file: enforcing Policy MLS status: enabled Policy deny_unknown status: allowed Memory protection checking: actual (secure) Max kernel policy version: 31 Then remove the –live-restore line from the /etc/sysconfig/docker ...

$ systemctl start docker $ systemctl status docker $ docker pull mysql $ docker image ls $ docker run --name db -e MYSQL_ROOT_PASSWORD=mysql123 -d mysql Use the docker exec -it command to start a mysql client inside the Docker container you have started, like the following: $ docker exec -it db mysql -uroot -p