-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Closed
Closed
Copy link
Labels
never-staleUse this label to ensure the stale action does not close this issueUse this label to ensure the stale action does not close this issue
Description
This is a: Bug
Details
INFO: FTL branch: master
INFO: FTL version: v6.0.4
INFO: FTL commit: b7eb53bf
INFO: FTL date: 2025-03-04 17:22:10 +0000
INFO: FTL user: pihole
INFO: Compiled for linux/amd64 (compiled on CI) using cc (Alpine 14.2.0) 14.2.0
Related Issues
- I have searched this repository/Pi-hole forums for existing issues and pull requests that look similar
How to reproduce the issue
- Environment data
- Operating System: Ubuntu
- Hardware: PC
- Kernel Architecture: amd64
- Docker Install Info and version:
- Software source: official docker-ce, OS provided package
- Supplimentary Software:
- Hardware architecture: amd64
- docker-compose.yml contents, docker run shell command, or paste a screenshot of any UI based configuration of containers here
sudo docker compose up --detach pihole
services:
pihole:
container_name: pihole
image: pihole/pihole
network_mode: host
cap_add:
- NET_ADMIN # In this case, the `NET_ADMIN` capability is added, which allows the container to perform various network-related tasks.
- NET_BIND_SERVICE # Allows FTLDNS binding to TCP/UDP sockets below 1024 (specifically DNS service on port 53)
- NET_RAW # use raw and packet sockets (needed for handling DHCPv6 requests, and verifying that an IP is not in use before leasing it)
# - NET_ADMIN # modify routing tables and other network-related operations (in particular inserting an entry in the neighbor table to answer DHCP requests using unicast packets)
- SYS_NICE # FTL sets itself as an important process to get some more processing time if the latter is running low
- CHOWN # we need to be able to change ownership of log files and databases in case FTL is started as a different user than pihole
- NET_BROADCAST # DHCP broadcast Make socket broadcasts, and listen to multicasts.
- CAP_SYS_TIME # WARNING Insufficient permissions to set system time (CAP_SYS_TIME required), NTP client not available
- CAP_SETGID
- CAP_SETUID
restart: unless-stopped
# RAM shortage (/dev/shm) ahead: 99% used
# /dev/shm: 268.1MB used, 268.4MB total, FTL uses 268.1MB
# Set the shared memory size to 1G
# Resizing "FTL-queries" from 1007648768 to (17997824 * 56) == 1007878144 (/dev/shm: 1.0GB used, 1.1GB total, FTL uses 1.0GB)
# WARNING: RAM shortage (/dev/shm) ahead: 93% is used (/dev/shm: 1.0GB used, 1.1GB total, FTL uses 1.0GB)
# add_message(type=7, message=/dev/shm) - SQL error step DELETE: database is locked
# Error while trying to close database: database is locked
# Resizing "FTL-queries" from 1007878144 to (18001920 * 56) == 1008107520 (/dev/shm: 1.0GB used, 1.1GB total, FTL uses 1.0GB)
# WARNING: RAM shortage (/dev/shm) ahead: 93% is used (/dev/shm: 1.0GB used, 1.1GB total, FTL uses 1.0GB)
shm_size: "2G"
environment:
FTLCONF_debug_caps: true
PIHOLE_UID: 999
PIHOLE_GID: 999
FTLCONF_ntp_ipv4_active: false
FTLCONF_ntp_ipv6_active: false
FTLCONF_ntp_sync_active: false
FTLCONF_dns_cache_optimizer: '0'
FTLCONF_dhcp_rapidCommit: true
FTLCONF_webserver_interface_theme: "default-auto"
FTLCONF_webserver_interface_boxed: false
PIHOLE_PTR: "HOSTNAMEFQDN"
FTLCONF_misc_nice: "-1"
volumes:
- type: bind
source: /etc/timezone
target: /etc/timezone
read_only: true
- type: bind
source: /etc/localtime
target: /etc/localtime
read_only: true
- pihole:/etc/pihole/
cpu_shares: 2048
volumes:
pihole:
- any additional info to help reproduce
These common fixes didn't work for my issue
- I have tried removing/destroying my container, and re-creating a new container
- I have tried fresh volume data by backing up and moving/removing the old volume data
- I have tried running the stock
docker run
example(s) in the readme (removing any customizations I added) - I have tried a newer or older version of Docker Pi-hole (depending what version the issue started in for me)
- I have tried running without my volume data mounts to eliminate volumes as the cause
If the above debugging / fixes revealed any new information note it here.
Add any other debugging steps you've taken or theories on root cause that may help.
INFO: Parsed config file /etc/pihole/pihole.toml successfully
CRIT: pihole-FTL is already running (PID 49)!
[i] pihole-FTL exited with status 1
[i] Container will now stop or restart depending on your restart policy
https://docs.docker.com/engine/containers/start-containers-automatically/#use-a-restart-policy
srstsavage
Metadata
Metadata
Assignees
Labels
never-staleUse this label to ensure the stale action does not close this issueUse this label to ensure the stale action does not close this issue