Subj : Help - Broke my docker-compose/podman-compose environment
To   : All
From : Errol Casey
Date : Tue Nov 19 2024 08:51:44

  Re: Help - Broke my docker-compose/podman-compose environment
  By: Errol Casey to All on Sat Nov 16 2024 02:29 pm

 Al> I use podman vs docker but they are very similar.

 Al> Had a reverse proxy setup working, and due to issue ssl cert ended up
 Al> getting things out of whack.

 Al> Got things cleaned up, and I can restart it but it acts like it has issues
 Al> with binding?  I've tried to make sure everything is down but still get
 Al> this error when I restart:

 Al> podman-compose up -d
 Al> da017bc9e305adb8a963d88f45993d50f74eeb76b4e19684c09188f7dad75418 Port
 Al> mappings have been discarded as one of the Host, Container, Pod, and None
 Al> network modes are in use
 Al> ab05a612b9245635423988fab582b0750af4b36f4627c32102ebffe7dc52bd90
 Al> 294585f5122dbeeb475e828ddaf5a3602538a0da7a3cf155c1907c1fc6cd
Turned out to be that a system configuration file in /etc/sysctl.d
was named incorrectly; and after a reboot.

Rootless docker containers could not bind to port 80. Once I renamed
the file with suffix .conf, and executed sysctl --system. I was
back in business.
-- 
Amessyroom - Sysop
toolazy.synchro.net:22 (ssh) 
toolazy.synchro.net:2323 (telnet)  
https://toolazy.synchro.net
--- SBBSecho 3.22-Linux
 * Origin: Too Lazy BBS - toolazy.synchro.net:2323 (1337:3/194)

.