2.5-sc, v2.5.9-sc (2.5-sc/Dockerfile)
2.5-ss, v2.5.9-ss (2.5-ss/Dockerfile)
v3.0, v3.0.7, latest (Dockerfile)
Firebird Project is happy to announce general availability of Firebird 3.0.7 — the latest point release in the Firebird 3.0 series.
This sub-release offers many bug fixes and also adds a few improvements, please refer to the Release Notes for the full list of changes. Binary kits for Windows, Linux, Mac OS and Android platforms are immediately available for download.
All users of Firebird v3.0.6 are strongly encouraged to upgrade to v3.0.7 as soon as possible due to several serious bugs found in v3.0.6 and fixed in this point release.
The Firebird Project is happy to announce the general availability of Firebird 2.5.9 — the latest minor release in the Firebird 2.5 series.
This sub-release introduces several bug fixes and a few improvements, please refer to the Release Notes for the full list of changes. Binary kits for Windows, Linux and MacOS X (both 32-bit and 64-bit) are immediately available for download.
Also, in accordance with its release lifetime policy, the Firebird Project advises that the Firebird v2.5 series has reached its end-of-life and thus will not be maintained further. Once Firebird 4.0 is released, this last official release in the v.2.5 series, Firebird 2.5.9, will be moved to the "Discontinued Versions" section of the download area.
The default password for sysdba is randomly generated when you first launch the container,
look in the docker log for your container or check /firebird/etc/SYSDBA.password.
Alternatively you may pass the environment variable ISC_PASSWORD to set the default password.
I will maintain current versions of Stable firebird releases. Each version of the stable branches will recieve a tag on both github and docker that will be semi permanent. The latest tagged versions will periodically be deleted and remade if a new feature for the image is created. Tags other than the latest release will not be updated as image specific features are implemented
Any new image features will be developed on the 3.0 releases
The 2.5 series was eol'd by the firebird guys as of the 2.5.9 release. I do not anticipate any further updates to the 2.5 images.
4.0 has finally entered beta and along with it has some pretty major changes including ODS changes requiring a complete backup and restore to upgrade. Because of this I am taking the opportunity to update the underlying debian image to debian buster. Currently the image builds but I have not tested using it yet. In the coming months I will start making it usable. I hope to have the 4.0 image usable by the time the official sources are at release candidate status.
This is a Firebird SQL Database container.
Username: SYSDBA
Password is either set by ISC_PASSWORD or randomized
TimeZone. (i.e. America/Chicago)
Default sysdba user password, if left blank a random 20 character password will be set instead.
The password used will be placed in /firebird/etc/SYSDBA.password.
If a random password is generated then it will be in the log for the container.
If this is set then a database will be created with this name under the /firebird/data volume with the 'UTF8'
default character set and if FIREBIRD_USER is also set then FIREBIRD_USER will be given ownership.
This user will be created and given ownership of FIREBIRD_DATABASE.
This variable is only used if FIREBIRD_DATABASE is also set.
The password for FIREBIRD_USER, if left blank a random 20 character password will be set instead.
If a random password is generated then it will be in the log for the container.
If this is set to true then when launching without an existing /firebird/etc folder this will cause the newly created firebird.conf to have the following defaults:
AuthServer = Legacy_Auth, Srp, Win_Sspi
AuthClient = Legacy_Auth, Srp, Win_Sspi
UserManager = Legacy_UserManager, Srp
WireCrypt = enabled
This will allow legacy clients to connect and authenticate.
If this is set to true then when launching without an existing /firebird/etc folder this will cause the newly created firebird.conf to have
WireCrypt = enabled to allow compatibility with Jaybird 3
If set to the path to a file then the named variable minus the _FILE portion will contain the contents of that file.
This is useful for using docker secrets to manage your password.
This applies to all variables except TZ
At the moment only the "Super Classic" and "Super Server" architectures are available.
Super Classic.
Super Server.
Classic Server.
This single volume supercedes all of the old volumes with most of the old volumes existing as subdirectories under /firebird
Default location to put database files
security database DIR
config files DIR message files DIR
log files DIR
For some users they may prefer to run the filesystem in read only mode for additional security. These volumes would need to be created rw in order to do this.
This volume does not actually exist by default but you may want to create it if you wish to use a read only root filesystem
guardian lock DIR
This volume does not actually exist by default but you may want to create it if you wish to use a read only root filesystem
Database lock directory
I have now added HEALTHCHECK support to the image. By default it uses nc to check port 3050.
If you would like it to perform a more thorough check then you can create /firebird/etc/docker-healthcheck.conf
If you add HC_USER HC_PASS and HC_DB to that file then the healthcheck will attempt a simple query against the specified database to determine server status.
Example docker-healthcheck.conf:
HC_USER=SYSDBA
HC_PASS=masterkey
HC_DB=employee.fdb
Please note for events to work properly you must either configure RemoteAuxPort and forward it with -p using a direct mapping where both sides internal and external use the same port or use --net=host to allow the random port mapping to work. see: http://www.firebirdfaq.org/faq53/ for more information on event port mapping.