Docker Deep Dive - Container Networking Containers need to talk to each other. Sometimes they even need to talk to VMs and physicals and even the internet. On the flip side sometimes those VMs, physicals and the internet they need to talk back to containers. To help with that we have got a bunch of container networking options. Network Types in Docker Bridge Network: Sometimes we call this as single house networking.It's turned on by default. SO you have got a host and it's running docker right. It's got a built-in network called bridge or NAT in windows. Each container gets its own IP on the bridge network.They can all talk to each other. But containers on seperate bridges? That's a bit of a hassle because each one of this bridges is isolated, so these two we can see are isolated layer two networks and it would be the same even if they were on the same host. The only way to get in or out is to map ports to the host. This is ok but not very ...
Two Main Reason : One (Might Not Be Hacked) : Just change Config it will work as given in this link https://dba.stackexchange.com/questions/83984/connect-to-postgresql-server-fatal-no-pg-hba-conf-entry-for-host Second (Might Be Hacked) Oney way to find that is list users and check postgres=# \du It will list users. If you find " pgdbadm " user good chance your PostgreSQL got hacked One main thing they mainly do is they will add these two rules in begining of the pg_hba.conf file Hack Code host all postgres 0.0.0.0/0 reject host all pgdbadm 0.0.0.0/0 md5 For more info check the below links https://gist.github.com/andywer/1c7aaa23e758f555b483e171c51514e7 https://dba.stackexchange.com/questions/215294/why-does-pg-hba-conf-sometimes-have-random-rules-added-to-it-postgresql https://stackoverflow.com/questions/52197486/fatal-pg-hba-conf-rejects-connection-for-host-127-0-0-1-user-postgres-dat
Comments
Post a Comment