Suggestion: Separate Bitcoin Core from ckpool/ckstat docker

[SearchAndDestroy]

Would it be possible to have a docker container for Bitcoin Core/Knots and a 2nd for just ckpool and ckstats?
Right now I have to edit both ckpool/Dockerfile and ckstat/Dockerfile if I want to switch to Bitcoin Core 28.1 or even use Bitcoin Knots instead.
I think it would be much better to have the Bitcoin Core/Knots as container and have ckpool and ckstats together in a 2nd container.
I updated the 2 Dockerfile to use 28.1 and I am still syncing the blockchain though but I suspect it will work correctly.

[Casraw]

I was thinking about that but decided not to split it. But yes i will update it soon

[SearchAndDestroy]

Thank you. I'll update after it's finished syncing. Using a docker container like this one would simplify the upgrade process though but I respect your decision to not split.
https://github.com/dobtc/bitcoin

[CryptoDjama]

Hi @Casraw! 👋

I’ve manually updated Bitcoin Core to version 28.1 for my solo mining setup based on your ckpool repo (thank you again for your amazing work!).

After the update, the web interface (localhost:4000) stopped working. Everything else seems to be functioning correctly — I’m connected with ASICs and mining — but I want to be 100% sure that if I find a block, it will be correctly assigned to me and not lost due to any misconfiguration.

Could you please take a quick look and let me know if everything looks okay from your point of view?

Thank you so much in advance!
– @CryptoDjama

[CryptoDjama]

[SearchAndDestroy]

I also used bitcoin core 28.1 for my initial setup (I changed 4 lines in the 2 Dockerfile) and had no problems at all. Running on Ubunbu 25.04 on a LattePanda Sigma with 32gb ram on a 4Tb SSD.
I switched to Bitcoin Knots 28.1 by removing the docker images, cleaned the ./ckpool/data folder but kept the blocks and chainstats folder, recreated the docker containers via docker-compose and now docker logs ckstats-bitcoin gives me this. The pool itself is perfectly working and accepting shares.

[CryptoDjama]

I downloaded it manually and added it to the Dockerfile, now I can't see the interface

[SearchAndDestroy]

I use this for both ckpool and ckstats/Dockerfile. It's the Bitcoin Knots binary but you can substitute it for the Bitcoin Core one. I don't remember the exact URL though. I know I have the same for both architecture but the LattePanda is AMD64.

[CryptoDjama]

I already have a new version, I think I need to specify the correct path for statistics, but I don't know how, I tried using AI

[webhostsg]

I also used bitcoin core 28.1 for my initial setup (I changed 4 lines in the 2 Dockerfile) and had no problems at all. Running on Ubunbu 25.04 on a LattePanda Sigma with 32gb ram on a 4Tb SSD. I switched to Bitcoin Knots 28.1 by removing the docker images, cleaned the ./ckpool/data folder but kept the blocks and chainstats folder, recreated the docker containers via docker-compose and now docker logs ckstats-bitcoin gives me this. The pool itself is perfectly working and accepting shares.

Did you find a solution to the error? I'm having the same database connection issue. Pool is running fine though.

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-08-21 12:09:30.800 UTC [1] LOG:  starting PostgreSQL 13.21 (Debian 13.21-1.pgdg130+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit
2025-08-21 12:09:30.801 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-08-21 12:09:30.801 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2025-08-21 12:09:30.803 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-08-21 12:09:30.808 UTC [26] LOG:  database system was shut down at 2025-08-21 12:08:03 UTC
2025-08-21 12:09:30.813 UTC [1] LOG:  database system is ready to accept connections

Database connection error: Error: connect ECONNREFUSED 127.0.0.1:5432
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1637:16)
    at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '127.0.0.1',
  port: 5432
}
Error adding user: Error: connect ECONNREFUSED 127.0.0.1:5432
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1637:16)
    at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '127.0.0.1',
  port: 5432
}

[CryptoDjama]

I couldn't solve the problem, I'm monitoring the work of localhost:4001, I would like to audit my pool, I've been running rented power for six months now but haven't caught a block yet

[webhostsg]

I couldn't solve the problem, I'm monitoring the work of localhost:4001, I would like to audit my pool, I've been running rented power for six months now but haven't caught a block yet

Ok, thanks for the reply. May the Luck be with you!