Since your data on the CD will be static, I would use the following way :

Write a small, simplish JavaScript search engine, which has the image and search data hardcoded as arrays. The data part of the JavaScript lands in the search.html file in <script> tags, while the "search engine" is in a separate .js file. The database is statically created via a Perl script from your main database, this of course means that you will have to modify the build process for your CDrom and run the magic database creation Perl script before burning the stuff.

This solution would have the benefit that you can also create a static subindex (in HTML) where the images are listed after different criteria, and you essentially become platform independent (that is, as long as you don't use fancy CSS and/or fancy JavaScript).

The other solution would be to burn IndigoPerl and the built-in Apache server on the CD, but then your users would need to start the Apache server before they could access the CD - a suboptimal solution IMO.