Image Bugs
The English user guide is currently in beta preview. Most of the documents have been automatically translated from the Japanese version. Should you find any inaccuracies, please reach out to Flatt Security.
When you find a problem in an image, first separate whether it is behavior of the packaged software itself or behavior introduced by the image packaging.
Bugs in the upstream software
Behavior of the included software itself, such as an option not working as expected or a crash on specific input, originates in the upstream software. Except for urgent security patches, GMO Flatt Security generally builds from upstream source without adding proprietary changes. Such bugs are therefore expected to exist in the upstream source code as well.
As a rule, report these issues to the upstream project. GMO Flatt Security also understands itself as a member of the open-source community, and will coordinate, assist, and contribute toward fixes when possible.
Image-specific configuration bugs
GMO Flatt Security handles bugs that depend on the image-specific configuration. Examples include:
- Bugs caused by the combination of included dependency versions.
- Bugs caused by bundled certificates.
- Incorrect image specifications, such as the entrypoint or environment variables.
- Bugs introduced by an image build error.
These are not upstream source-code bugs; they are introduced while assembling the software as an image. If you believe an issue falls into this category, contact GMO Flatt Security support.