Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG] bunkerweb container health status is not accurate when using autoconf #1826

Open
2 tasks done
cinderisles opened this issue Dec 24, 2024 · 3 comments
Open
2 tasks done

[BUG] bunkerweb container health status is not accurate when using autoconf #1826

cinderisles opened this issue Dec 24, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@cinderisles
Copy link

cinderisles commented Dec 24, 2024 •
edited
Loading

What happened?

Using the config from the Docker autoconf docker-compose configuration from the documentation, the autoconf container never starts because the main bunkerweb container is not healthy

Keep in mind that I am using rootless podman, and havent tried this with docker. I am unsure if this is podman-specific and hope someone here can help reproduce

Here are the logs from the autoconf container. This repeats infinitely

[2024-12-24 20:11:58 +0000] [DOCKER-CONTROLLER] [1] [⚠️ ] - Instance autoconf-bunkerweb-1 is not ready, waiting 5s ...
[2024-12-24 20:12:03 +0000] [DOCKER-CONTROLLER] [1] [⚠️ ] - Instance autoconf-bunkerweb-1 is not ready, waiting 5s ...
[2024-12-24 20:12:08 +0000] [DOCKER-CONTROLLER] [1] [⚠️ ] - Instance autoconf-bunkerweb-1 is not ready, waiting 5s ...

Here is the line of code that produces the above error message: Controller.py

And here is the line that seems to be responsible for telling the autoconf container about bunkerweb's health status: DockerController.py

The problem is that this line is resolving to false because the value of State.Health.Status in podman inspect <bunkerweb container> is an empty string. That line checks if State.Running == true and State.Health.Status == "healthy"

Here is my bunkweb container info

"State": {
     "OciVersion": "1.1.0+dev",
     "Status": "running",
     "Running": true,
     "Paused": false,
     "Restarting": false,
     "OOMKilled": false,
     "Dead": false,
     "Pid": 5645,
     "ConmonPid": 5643,
     "ExitCode": 0,
     "Error": "",
     "StartedAt": "2024-12-24T13:03:12.2350236-06:00",
     "FinishedAt": "0001-01-01T00:00:00Z",
     "Health": {
          "Status": "",
          "FailingStreak": 0,
          "Log": null
     },
     "CgroupPath": "/user.slice/user-1000.slice/user@1000.service/app.slice/podman.service",
     "CheckpointedAt": "0001-01-01T00:00:00Z",
     "RestoredAt": "0001-01-01T00:00:00Z"
},

I am trying to figure out if this is a problem with bunkerweb, or podman, or just my config. I did try manually running the healthcheck script of bunkerweb and it seems to be okay --- just the status is not actually being updated on the container, even though the Dockerfile has this healthcheck line

Here's how I manually ran the healthcheck

first made sure that podman will actually report back the correct exit code

$ podman exec <bunkerweb container> sh -c "exit 100"; echo $?"
100

then checked the code of the healthcheck

$ podman exec <bunkerweb container> sh -c "./helpers/healthcheck.sh"; echo $?"
0

The next thing I am going to try is to run the healthcheck from docker-compose instead the one defined on the image. Maybe healthchecks in images dont run if you use docker-compose? Not sure, im looking into it. Will someone try this with Docker just to rule out this being a podman issue?

How to reproduce?

Use the docker-compose yaml from the documentation and rootless Podman

https://docs.bunkerweb.io/latest/integrations/#docker-autoconf

Configuration file(s) (yaml or .env)

version: "3.5"

services:
  bunkerweb:
    image: bunkerity/bunkerweb:1.5.12
    ports:
      - 80:8080
      - 443:8443
    labels:
      - "bunkerweb.INSTANCE=yes"
    environment:
      - SERVER_NAME=
      - DATABASE_URI=mariadb+pymysql://bunkerweb:changeme@bw-db:3306/db
      - AUTOCONF_MODE=yes
      - MULTISITE=yes
      - API_WHITELIST_IP=127.0.0.0/8 10.20.30.0/24
    networks:
      - bw-universe
      - bw-services

  bw-autoconf:
    image: bunkerity/bunkerweb-autoconf:1.5.12
    depends_on:
      - bunkerweb
      - bw-docker
    environment:
      - DATABASE_URI=mariadb+pymysql://bunkerweb:changeme@bw-db:3306/db
      - AUTOCONF_MODE=yes
      - DOCKER_HOST=tcp://bw-docker:2375
    networks:
      - bw-universe
      - bw-docker

  bw-scheduler:
    image: bunkerity/bunkerweb-scheduler:1.5.12
    depends_on:
      - bunkerweb
      - bw-docker
    environment:
      - DATABASE_URI=mariadb+pymysql://bunkerweb:changeme@bw-db:3306/db
      - DOCKER_HOST=tcp://bw-docker:2375
      - AUTOCONF_MODE=yes
    networks:
      - bw-universe
      - bw-docker

  bw-docker:
    image: tecnativa/docker-socket-proxy:nightly
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
    environment:
      - CONTAINERS=1
      - LOG_LEVEL=warning
    networks:
      - bw-docker

  bw-db:
    image: mariadb:10.10
    environment:
      - MYSQL_RANDOM_ROOT_PASSWORD=yes
      - MYSQL_DATABASE=db
      - MYSQL_USER=bunkerweb
      - MYSQL_PASSWORD=changeme
    volumes:
      - bw-data:/var/lib/mysql
    networks:
      - bw-docker

volumes:
  bw-data:

networks:
  bw-universe:
    name: bw-universe
    ipam:
      driver: default
      config:
        - subnet: 10.20.30.0/24
  bw-services:
    name: bw-services
  bw-docker:
    name: bw-docker

Relevant log output

[2024-12-24 19:03:12] - ENTRYPOINT - ℹ️ - Starting BunkerWeb v1.5.12 ...
[2024-12-24 19:03:12] - ENTRYPOINT - ℹ️ - Setup and check /data folder ...
[2024-12-24 19:03:12 +0000] [GENERATOR] [10] [ℹ️ ] - Generator started ...
[2024-12-24 19:03:12 +0000] [GENERATOR] [10] [ℹ️ ] - Settings : /usr/share/bunkerweb/settings.json
[2024-12-24 19:03:12 +0000] [GENERATOR] [10] [ℹ️ ] - Templates : /usr/share/bunkerweb/confs
[2024-12-24 19:03:12 +0000] [GENERATOR] [10] [ℹ️ ] - Core : /usr/share/bunkerweb/core
[2024-12-24 19:03:12 +0000] [GENERATOR] [10] [ℹ️ ] - Plugins : /etc/bunkerweb/plugins
[2024-12-24 19:03:12 +0000] [GENERATOR] [10] [ℹ️ ] - Pro plugins : /etc/bunkerweb/pro/plugins
[2024-12-24 19:03:12 +0000] [GENERATOR] [10] [ℹ️ ] - Output : /etc/nginx
[2024-12-24 19:03:12 +0000] [GENERATOR] [10] [ℹ️ ] - Target : /etc/nginx
[2024-12-24 19:03:12 +0000] [GENERATOR] [10] [ℹ️ ] - Variables : /tmp/variables.env
[2024-12-24 19:03:12 +0000] [GENERATOR] [10] [ℹ️ ] - Checking arguments ...
[2024-12-24 19:03:12 +0000] [GENERATOR] [10] [ℹ️ ] - Computing config ...
[2024-12-24 19:03:12 +0000] [GENERATOR] [10] [ℹ️ ] - Removing old files ...
[2024-12-24 19:03:12 +0000] [GENERATOR] [10] [ℹ️ ] - Rendering templates ...
[2024-12-24 19:03:12 +0000] [GENERATOR] [10] [ℹ️ ] - Generator successfully executed !
[2024-12-24 19:03:12] - ENTRYPOINT - ℹ️ - Starting nginx ...
2024/12/24 19:03:12 [notice] 47#47: ModSecurity-nginx v1.0.3 (rules loaded inline/local/remote: 0/0/0)
2024/12/24 20:03:30 [error] 190#190: recv() failed (111: Connection refused) while resolving, resolver: 127.0.0.11:53
2024/12/24 20:03:35 [error] 190#190: recv() failed (111: Connection refused) while resolving, resolver: 127.0.0.11:53
2024/12/24 20:03:40 [error] 190#190: recv() failed (111: Connection refused) while resolving, resolver: 127.0.0.11:53
2024/12/24 20:03:40 [error] 177#177: *23213 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 174#174: *23229 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 167#167: *23224 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 192#192: *23197 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 168#168: *23201 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 181#181: *23205 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 197#197: *23198 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 188#188: *23250 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 171#171: *23226 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 178#178: *23199 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 195#195: *23196 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 175#175: *23236 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 182#182: *23233 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 176#176: *23235 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 186#186: *23200 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 189#189: *23202 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 179#179: *23231 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 194#194: *23203 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 184#184: *23227 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 191#191: *23192 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 193#193: *23194 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 172#172: *23228 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 173#173: *23204 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 196#196: *23195 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 187#187: *23214 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 183#183: *23245 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 180#180: *23242 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 169#169: *23225 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 185#185: *23253 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 166#166: *23223 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:40 [error] 170#170: *23239 [INIT-WORKER] lock:lock() failed : timeout, context: ngx.timer
2024/12/24 20:03:45 [error] 190#190: recv() failed (111: Connection refused) while resolving, resolver: 127.0.0.11:53
2024/12/24 20:03:50 [error] 190#190: recv() failed (111: Connection refused) while resolving, resolver: 127.0.0.11:53
2024/12/24 20:03:55 [error] 190#190: recv() failed (111: Connection refused) while resolving, resolver: 127.0.0.11:53
2024/12/24 20:04:00 [error] 190#190: *23193 [INIT-WORKER] bunkernet:init_worker() call failed : error while sending request to API : error while sending request : api.bunkerweb.io could not be resolved (110: Operation timed out), context: ngx.timer
2024/12/24 20:04:00 [error] 190#190: *23193 recv() failed (111: Connection refused), context: ngx.timer
2024/12/24 20:04:00 [error] 190#190: *23193 [UTILS] error while doing A DNS query for 2.0.0.127.bl.blocklist.de : failed to receive reply from UDP server 127.0.0.11:53: connection refused, context: ngx.timer
2024/12/24 20:04:00 [error] 190#190: *23193 recv() failed (111: Connection refused), context: ngx.timer
2024/12/24 20:04:00 [error] 190#190: *23193 [UTILS] error while doing A DNS query for 2.0.0.127.problems.dnsbl.sorbs.net : failed to receive reply from UDP server 127.0.0.11:53: connection refused, context: ngx.timer
2024/12/24 20:04:00 [error] 190#190: *23193 recv() failed (111: Connection refused), context: ngx.timer
2024/12/24 20:04:00 [error] 190#190: *23193 [UTILS] error while doing A DNS query for 2.0.0.127.sbl.spamhaus.org : failed to receive reply from UDP server 127.0.0.11:53: connection refused, context: ngx.timer
2024/12/24 20:04:00 [error] 190#190: *23193 recv() failed (111: Connection refused), context: ngx.timer
2024/12/24 20:04:00 [error] 190#190: *23193 [UTILS] error while doing A DNS query for 2.0.0.127.xbl.spamhaus.org : failed to receive reply from UDP server 127.0.0.11:53: connection refused, context: ngx.timer
2024/12/24 20:04:00 [error] 190#190: *23193 [DNSBL] dnsbl check for problems.dnsbl.sorbs.net failed, context: ngx.timer
2024/12/24 20:04:00 [error] 190#190: *23193 [DNSBL] dnsbl check for bl.blocklist.de failed, context: ngx.timer
2024/12/24 20:04:00 [error] 190#190: *23193 [DNSBL] dnsbl check for sbl.spamhaus.org failed, context: ngx.timer
2024/12/24 20:04:00 [error] 190#190: *23193 [DNSBL] dnsbl check for xbl.spamhaus.org failed, context: ngx.timer
2024/12/24 20:04:00 [notice] 190#190: *23193 [INIT-WORKER] BunkerWeb is ready to fool hackers ! 🚀, context: ngx.timer

BunkerWeb version

1.5.12

What integration are you using?

Autoconf

Linux distribution (if applicable)

No response

Removed private data

  • I have removed all private data from the configuration file and the logs

Code of Conduct

  • I agree to follow this project's Code of Conduct
@cinderisles cinderisles added the bug Something isn't working label Dec 24, 2024
@cinderisles
Copy link
Author

Adding the healthcheck to docker-compose seems to have fixed it

services:
  bunkerweb:
    image: bunkerity/bunkerweb:1.5.12
    ports:
      - 80:8080
      - 443:8443
    labels:
      - "bunkerweb.INSTANCE=yes"
    environment:
      - SERVER_NAME=
      - DATABASE_URI=mariadb+pymysql://bunkerweb:changeme@bw-db:3306/db
      - AUTOCONF_MODE=yes
      - MULTISITE=yes
      - API_WHITELIST_IP=127.0.0.0/8 10.20.30.0/24
    networks:
      - bw-universe
      - bw-services
    healthcheck:
      test: /usr/share/bunkerweb/helpers/healthcheck.sh
      interval: 10s
      timeout: 10s
      start_period: 10s
      retries: 6

autoconf logs

[2024-12-24 21:03:12 +0000] [DOCKER-CONTROLLER] [1] [⚠️ ] - Instance autoconf-bunkerweb-1 is not ready, waiting 5s ...
[2024-12-24 21:03:17 +0000] [DOCKER-CONTROLLER] [1] [⚠️ ] - Instance autoconf-bunkerweb-1 is not ready, waiting 5s ...
[2024-12-24 21:03:22 +0000] [AUTOCONF] [1] [ℹ️ ] - BunkerWeb instances are ready 🚀
[2024-12-24 21:03:22 +0000] [AUTOCONF] [1] [ℹ️ ] - Instance #1 : autoconf-bunkerweb-1
[2024-12-24 21:03:22 +0000] [AUTOCONF] [1] [ℹ️ ] - Processing events ...
[2024-12-24 21:03:22 +0000] [AUTOCONF] [1] [ℹ️ ] - BunkerWeb instances are ready 🚀
[2024-12-24 21:03:22 +0000] [AUTOCONF] [1] [ℹ️ ] - Instance #1 : autoconf-bunkerweb-1
[2024-12-24 21:03:22 +0000] [AUTOCONF] [1] [ℹ️ ] - Processing events ...
[2024-12-24 21:03:22 +0000] [AUTOCONF] [1] [ℹ️ ] - Instance #1 : autoconf-bunkerweb-1
[2024-12-24 21:03:22 +0000] [AUTOCONF] [1] [ℹ️ ] - Processing events ...
[2024-12-24 21:03:29 +0000] [DOCKER-CONTROLLER] [1] [ℹ️ ] - Caught Docker event, deploying new configuration ...
[2024-12-24 21:03:29 +0000] [CONFIG] [1] [⚠️ ] - Variable PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin is not a valid setting, ignoring it
[2024-12-24 21:03:22 +0000] [AUTOCONF] [1] [ℹ️ ] - Processing events ...
[2024-12-24 21:03:29 +0000] [DOCKER-CONTROLLER] [1] [ℹ️ ] - Caught Docker event, deploying new configuration ...
[2024-12-24 21:03:29 +0000] [CONFIG] [1] [⚠️ ] - Variable PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin is not a valid setting, ignoring it
[2024-12-24 21:03:29 +0000] [CONFIG] [1] [⚠️ ] - Variable container: podman is not a valid setting, ignoring it
[2024-12-24 21:03:29 +0000] [DOCKER-CONTROLLER] [1] [ℹ️ ] - Caught Docker event, deploying new configuration ...
[2024-12-24 21:03:29 +0000] [CONFIG] [1] [⚠️ ] - Variable PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin is not a valid setting, ignoring it
[2024-12-24 21:03:29 +0000] [CONFIG] [1] [⚠️ ] - Variable container: podman is not a valid setting, ignoring it
[2024-12-24 21:03:29 +0000] [CONFIG] [1] [⚠️ ] - Variable PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin is not a valid setting, ignoring it
[2024-12-24 21:03:29 +0000] [CONFIG] [1] [⚠️ ] - Variable container: podman is not a valid setting, ignoring it
[2024-12-24 21:03:29 +0000] [CONFIG] [1] [⚠️ ] - Variable container: podman is not a valid setting, ignoring it
[2024-12-24 21:03:29 +0000] [CONFIG] [1] [⚠️ ] - Variable NGINX_VERSION: 1.26.2 is not a valid setting, ignoring it
[2024-12-24 21:03:29 +0000] [CONFIG] [1] [⚠️ ] - Variable NGINX_VERSION: 1.26.2 is not a valid setting, ignoring it
[2024-12-24 21:03:29 +0000] [CONFIG] [1] [⚠️ ] - Variable PKG_RELEASE: 1 is not a valid setting, ignoring it
[2024-12-24 21:03:29 +0000] [CONFIG] [1] [⚠️ ] - Variable PKG_RELEASE: 1 is not a valid setting, ignoring it
[2024-12-24 21:03:29 +0000] [CONFIG] [1] [⚠️ ] - Variable DYNPKG_RELEASE: 2 is not a valid setting, ignoring it
[2024-12-24 21:03:29 +0000] [CONFIG] [1] [⚠️ ] - Variable DYNPKG_RELEASE: 2 is not a valid setting, ignoring it
[2024-12-24 21:03:29 +0000] [CONFIG] [1] [⚠️ ] - Variable HOME: /var/cache/nginx is not a valid setting, ignoring it
[2024-12-24 21:03:29 +0000] [CONFIG] [1] [⚠️ ] - Variable HOSTNAME: 7dbffa4292ec is not a valid setting, ignoring it
[2024-12-24 21:03:29 +0000] [DOCKER-CONTROLLER] [1] [ℹ️ ] - Successfully deployed new configuration 🚀

Maybe this is an issue with docker-compose and Podman and not Bunkerweb. If anyone else can reproduce this, maybe it's a note that could be added to the documentation. I'm going to configure the other healthchecks the same way and report back with the full docker-compose.yaml

@cinderisles
Copy link
Author

cinderisles commented Dec 24, 2024 •
edited
Loading

Here is the final docker compose file that also includes the bw-ui image. I have copied the healthchecks from each service's HEALTHCHECK line in their Dockerfile. Things seem to be working okay now. I don't know if this is a bug with Podman or just a quirk of healthchecks. I'm just glad I can start configuring bunkerweb for my own stuff. Hopefully this helps someone with a similar issue

services:
  bunkerweb:
    image: bunkerity/bunkerweb:1.5.12
    ports:
      - 80:8080
      - 443:8443
    labels:
      - "bunkerweb.INSTANCE=yes"
    environment:
      - SERVER_NAME=
      - DATABASE_URI=mariadb+pymysql://bunkerweb:changeme@bw-db:3306/db
      - AUTOCONF_MODE=yes
      - MULTISITE=yes
      - API_WHITELIST_IP=127.0.0.0/8 10.20.30.0/24
    networks:
      - bw-universe
      - bw-services
    healthcheck:
      test: /usr/share/bunkerweb/helpers/healthcheck.sh
      interval: 10s
      timeout: 10s
      start_period: 10s
      retries: 6

  bw-autoconf:
    image: bunkerity/bunkerweb-autoconf:1.5.12
    depends_on:
      - bunkerweb
      - bw-docker
    environment:
      - DATABASE_URI=mariadb+pymysql://bunkerweb:changeme@bw-db:3306/db
      - AUTOCONF_MODE=yes
      - DOCKER_HOST=tcp://bw-docker:2375
    networks:
      - bw-universe
      - bw-docker
    healthcheck:
      test: /usr/share/bunkerweb/helpers/healthcheck-autoconf.sh
      interval: 10s
      timeout: 10s
      start_period: 60s
      retries: 6

  bw-scheduler:
    image: bunkerity/bunkerweb-scheduler:1.5.12
    depends_on:
      - bunkerweb
      - bw-docker
    environment:
      - DATABASE_URI=mariadb+pymysql://bunkerweb:changeme@bw-db:3306/db
      - DOCKER_HOST=tcp://bw-docker:2375
      - AUTOCONF_MODE=yes
    networks:
      - bw-universe
      - bw-docker
    healthcheck:
      test: /usr/share/bunkerweb/helpers/healthcheck-scheduler.sh
      interval: 10s
      timeout: 10s
      start_period: 30s
      retries: 6

  bw-ui:
    image: bunkerity/bunkerweb-ui:1.5.12
    depends_on:
      - bw-docker
    environment:
      - DATABASE_URI=mariadb+pymysql://bunkerweb:changeme@bw-db:3306/db
      - DOCKER_HOST=tcp://bw-docker:2375
    networks:
      - bw-universe
      - bw-docker
    healthcheck:
      test: /usr/share/bunkerweb/helpers/healthcheck-ui.sh
      interval: 10s
      timeout: 10s
      start_period: 30s
      retries: 6

  bw-docker:
    image: tecnativa/docker-socket-proxy:nightly
    volumes:
      - $XDG_RUNTIME_DIR/podman/podman.sock:/var/run/docker.sock:ro
    environment:
      - CONTAINERS=1
      - LOG_LEVEL=warning
    env_file:
      - .env
    networks:
      - bw-docker

  bw-db:
    image: mariadb:10.10
    environment:
      - MYSQL_RANDOM_ROOT_PASSWORD=yes
      - MYSQL_DATABASE=db
      - MYSQL_USER=bunkerweb
      - MYSQL_PASSWORD=changeme
    volumes:
      - bw-data:/var/lib/mysql
    networks:
      - bw-docker

volumes:
  bw-data:

networks:
  bw-universe:
    name: bw-universe
    ipam:
      driver: default
      config:
        - subnet: 10.20.30.0/24
  bw-services:
    name: bw-services
  bw-docker:
    name: bw-docker

7dbffa4292ec  docker.io/bunkerity/bunkerweb:1.5.12                                   15 minutes ago      Up About a minute (healthy)  0.0.0.0:80->8080/tcp, 0.0.0.0:443->8443/tcp  autoconf-bunkerweb-1
83eaa2d1466e  docker.io/bunkerity/bunkerweb-ui:1.5.12          python3 -m gunico...  About a minute ago  Up About a minute (healthy)                                               autoconf-bw-ui-1
4786d5251fae  docker.io/bunkerity/bunkerweb-autoconf:1.5.12    python3 main.py       About a minute ago  Up About a minute (healthy)                                               autoconf-bw-autoconf-1
79244f72e312  docker.io/bunkerity/bunkerweb-scheduler:1.5.12                         About a minute ago  Up About a minute (healthy)                                               autoconf-bw-scheduler-1

@TheophileDiot
Copy link
Member

Hi, happy to see that you found a solution, indeed it looks like this is a podman specific issue. 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cinderisles @TheophileDiot