Document workaround for spring-projects/spring-boot#23130

spring-graalvm-native-docs/src/main/asciidoc/troubleshooting.adoc

@@ -26,6 +26,25 @@ The image can fail for a number of reasons. We have described the most common ca
 If your built image does not run, you can try a number of fixes.
 This section describes those possible fixes.
 
+=== Spring Boot image building fails when specifying <BP_BOOT_NATIVE_IMAGE_BUILD_ARGUMENTS>
+
+With some content specified in between `<BP_BOOT_NATIVE_IMAGE_BUILD_ARGUMENTS>` element in Spring Boot image configuration,
+the build can fail with an error like:
+
+====
+[source,bash]
+----
+[ERROR] Failed to execute goal org.springframework.boot:spring-boot-maven-plugin:2.4.0-M2:build-image (default-cli) on project rest-service:
+Execution default-cli of goal org.springframework.boot:spring-boot-maven-plugin:2.4.0-M2:build-image failed: Docker API call to
+'localhost/v1.24/images/pack.local/builder/otmkahcvlf:latest?force=1' failed with status code 404 "Not Found"
+----
+====
+
+This is due to https://github.com/spring-projects/spring-boot/issues/23130[this bug] that will be fixed asap.
+The workaround is to try to modify the content (change space to tabs, add or remove line breaks, etc.) to not hit that bug or
+to replace `<BP_BOOT_NATIVE_IMAGE_BUILD_ARGUMENTS>` element by a `META-INF/native-image/<GROUP_ID>/<ARTIFACT_ID>/native-image.properties`
+file with `Args = ...` content.
+
 ==== Missing resource bundles
 
 In some cases, when there is a problem, the error message tries to tell you exactly what to do, as follows: