I’ve been trying for a few days, digged the net, even chatGPT is cursing with me, so I’m trying here asking for help !
My goal is to self-host Invoice Ninja on my Raspberry Pi 5, in a docker, using Nginx Proxy Manager.
I have many services running on the RPI5 already, each in separated docker containers, all working fine. I have a wildcard SSL cert for a whole subdomain on my personal domain, works fine for other services on the same RPI5.
I’ve been trying very thorouhgly; first from scratch with the invoice-ninja:lastest image, had SSL issues (couldnt connect the IN docker to the IN-DB docker without SSL (something keeping me off deactivating the forced SSL). Then unable to actually have a proper SSL connection when trying, always resulted in a “connection denied” (certificate checked, sql password checked). In each case, IN container autorestarting again and again.
Then I discovered the gitn and the “docker” repo; restarted with it. Different flavours of errors along the way, but in the end, still having unfixable SQL connexion errors.
I’ve looked all I could find on the net; ChatGPT even begins to curse ^^’
Anyone has an idea or some direction to point me to ?
In Process.php line 269:
The command "mysql --user="${:LARAVEL_LOAD_USER}" --password="${:LARAVEL_L
OAD_PASSWORD}" --host="${:LARAVEL_LOAD_HOST}" --port="${:LARAVEL_LOAD_PORT}
" --database="${:LARAVEL_LOAD_DATABASE}" < "${:LARAVEL_LOAD_PATH}"" failed.
Exit Code: 1(General error)
Working directory: /var/www/app
Output:
================
Error Output:
================
mysql: Deprecated program name. It will be removed in a future release, use
'/usr/bin/mariadb' instead
ERROR 2026 (HY000): TLS/SSL error: self-signed certificate in certificate c
hain
I’m using the docker-compose file in the master branch of IN’s docker files repo, the only thing I’ve changed were the ports. (the new docker image @ the debian branch would spike the CPU’s usage to 100% and eventually crash. I’m also trying to restore a backup, and afaik the new docker image is not compatible with the previous).
I was able to successfully install InvoiceNinja by using an older tag (5.9.9, for no specific reason). I now bumped the tag to just 5 and it is running smoothly, so it seems this error only occurs during setup.
This workaround works fine, but this should be looked into. Lmk if you can reproduce this on your end. If not, I’d be happy to provide with detailed info about my system’s specs and/or logs.
@Blackbird, is your issue related to this? Does my workaround “fix” your problem?
master is deprecated, the alpine base image is too new for running the initialization. For a new instance it makes no sense to start with alpine. Debian or octane should work, but I’m not aware of a high cpu issue with them.
Yes I am ! On the second try I went for the standard docker file =)
I don’t seem to encounter the same error, though
@juoum Same error code indeed ! Until I worked my a$$ off to get a SSL cert downloaded, copied, mouted, self-signed and authentified but … just had a different error after ^^’
I’m not sure what you mean by using an older tag; version 5.9.9 ? This one here Release v5.9.9 · invoiceninja/invoiceninja · GitHub ?
Not sure how to pull it from my RPI, guess I can try; though it’s not meant to be ran on docker, doest it stand a chance ?
@benbrummer the regular docker file is meant for debian, isnt’it ? Or should I read anf try specifically the fils in the “debian” sub repo ?
(I can’t remember if my RPI5 is runnning ubuntu server or PiOS Server, but both are Debian after all.
Invoiceninja docker containers are based on debian images, alpine is deprecated and are not really maintained anymore. As no alpine imnage is pinned, 3.21 is breaking the initialization cause opf mysql/mariadb.
The debian based images are running arm64 and amd64. The host architecture is relevant. The host distribution (ubunbtu, PIOS, debian, redhat…) is irrelevant
