search

jacobalberty / firebird-docker

Firebird Dockerfile
130 stars 96 forks source link

use debian bullseye for base image #74

Closed mariuz closed 3 years ago

mariuz commented 3 years ago

at least for firebird 4

https://www.debian.org/releases/stable/

gedeffe commented 3 years ago

Hello, even for older versions of firebird, we are interested in an update of debian. Harbor registry displays 320 vulnerabilities (42 criticals) for Debian Jessie, and only 57 vulnerabilities (4 criticals) for Debian Bullseye.

jacobalberty commented 3 years ago

Bullseye would run into the same issues as #56 with the libicu breaking

jacobalberty commented 3 years ago

Looks like for 4.0 the preferred libicu is libicu63. So I will need to make a new version of icu52.sh to install libicu63 for 4.0 bullseye and purge libicu67. I'm opening a 3.0-bullseye branch shortly.

jacobalberty commented 3 years ago

I've made pull requests for both 3.0 and 4.0 branches now.

3.0 I'll need to switch my test environment over and give it a test to make sure no obvious breakage, but once that's done I'll go ahead and merge it

I need to verify the 4.0 stuff on ARM but I've tested it on amd64 by replacing my development environment (with pre existing database) and did not see any breakage so it's just a matter of making sure ARM is good to go and fixing any issues that may crop up on the ARM build.

2.5 has some issues with taking this approach. There is no post_build hook system to tie into. It'll take a bit of time for me to update 2.5 to the new build system

jacobalberty commented 3 years ago

Reopening while I work on 2.5 as well, though 4.0 and 3.0 are done. all v3.0 tags should be pushed to the hub within the next 5-10 minutes. 4.0 will take quite a bit longer due to the inclusion of arm builds. Possibly up to 5 hours.

jacobalberty commented 3 years ago

2.5-sc, 2.5-ss, 3.0 and 4.0 should all have bullseye as their base image now. I have added v2.5.9-sc-jessie and v2.5.9-ss-jessie tags that provide the old jessie base image just in case this does break something since I no longer have a working test bed of firebird 2.5 for validation.

gedeffe commented 3 years ago

Thanks Jacob. It is great to see this issue closed ;-)

For 2.5-sc at least, even if our tests doesn't cover full range of cases, it works well in our cases (index are not broken).