Answer
Two separate things are usually involved. First, make sure a solutionset.yaml file is present in the ifsinstaller folder (or referenced via the command line) — without one, the installer assumes every component is active and tries to deploy every available container, which isn't what you want for anything but a full install; the solutionset.yaml is normally found in your customer solution repository (under the fndbas component), accessible through Build Place. Second, if you don't actually intend to configure a real certificate at install time, the certificateFile and certificatePassword parameters can simply be commented out entirely (not just left blank) — neither is mandatory per the installer's own parameter documentation, and commenting them out avoids the installer trying (and failing) to process an empty/invalid certificate configuration.