1. Forum
  2. tqwNet
  3. TQW DOCKER

  • Help - Broke my docker-compose/podman-compose environment

    From Errol Casey@1337:3/194 to All on Sat Nov 16 14:29:33 2024
    I use podman vs docker but they are very similar.

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

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

    podman-compose up -d da017bc9e305adb8a963d88f45993d50f74eeb76b4e19684c09188f7dad75418
    Port mappings have been discarded as one of the Host, Container, Pod, and None network modes are in use ab05a612b9245635423988fab582b0750af4b36f4627c32102ebffe7dc52bd90 294585f5122dbeeb475e828ddaf5a3602538a0da7a3cf155c1907c1fc6cda06f


    any ideas?
    --
    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)
  • From Errol Casey@1337:3/194 to All on Tue Nov 19 08:51:44 2024
    Re: Help - Broke my docker-compose/podman-compose environment
    By: Errol Casey to All on Sat Nov 16 2024 02:29 pm

    I use podman vs docker but they are very similar.

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

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

    podman-compose up -d da017bc9e305adb8a963d88f45993d50f74eeb76b4e19684c09188f7dad75418 Port mappings have been discarded as one of the Host, Container, Pod, and None network modes are in use ab05a612b9245635423988fab582b0750af4b36f4627c32102ebffe7dc52bd90 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)