docker-adminer VS postgres

If you prefer Adminer, here is the command to run:

However... I find this a little cumbersome for smooth development, so I much prefer to use Adminer, which as you may have guessed by now, can be spun up in it's very own container. The setup is similar to how we set up the MariaDB container and you can check out the official docs for the details should you want to set it up in the terminal too. The only problem with doing this is that you must set up a named network and connect both the MariaDB container and the Adminer container to it so that they can communicate. I did it a few times just to see how it was, and it's a lot of work so I'll just briefly explain the part of creating a network, because you will see later that there is a much easier way to achieve the same results even if doing it all manually is far more educational.

I was trying to mount Adminer on my Nas, and I wanted to mirror the plugins folder, using this compose configuration:

Like to run the docker image Adminer which is a full-featured database management tool written in PHP(think phpMyAdmin).

Here a compose.yml doing what you want using Percona MySQL and Adminer (formerly phpMinAdmin) a full-featured database management tool written in PHP. Replace the images with the apps you want.

https://github.com/TimWolla/docker-adminer/issues/108#issuec...

Disclosure: I'm the TimWolla of the repository in the second link :-)

I have a hard time getting my head around Docker and ports, but I'm specifying ports the way the adminer docs suggest to. Here's my service entry:

To really learn and get easy feedback use your fav db docker image, postgres, mysql(percona) or sqlite(alpine) with adminer and some test data(insert.sql) in a git repo pushed to gitlab/github.

Caddy reverse proxying to adminer port 8080 should do the trick. Reference: https://hub.docker.com/_/adminer

EDIT: Somehow i managed to fix it right now (I struggled with this problem yesterday for hours). This github issue have helped: https://github.com/docker-library/postgres/issues/537 If anyone runs into this problem, those are crucial instructions that helped me: docker system prune docker-compose up --force-recreate --build --remove-orphans --always-recreate-deps --renew-anon-volumes

Tragedy of the commons - only need a few actors to ruin it all for us. Almost all distributors face this problem, from Docker Hub to PyPI. This also reminded me of official Postgres Docker image running a cryptominer in the background [1]

[1] - https://github.com/docker-library/postgres/issues/770

If you open the dockerfile of the desired container, you can determine exactly how and what was built. If not satisfied, you can always build your own container with the right postgresql build flags.

Ok according to The Dockerfile, postgres is running in /var/lib/postgresql/data so you will need enter the container and look at the log files in /var/lib/postgresql/data/pg_log/

I got started on trying to make a basic postgres image but I can't seem to figure out how to include a shell script in the same folder as my nix file (fetched from https://github.com/docker-library/postgres/blob/master/docker-entrypoint.sh and to be modified once I get it working) into the docker image as an entrypoint

See example here : https://github.com/docker-library/postgres/issues/601