You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs/ci-cd-guides/building-docker-images.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -187,7 +187,7 @@ An alternative way to create Docker images is to just package an existing artifa
187
187
188
188
>Notice that even though this is a very popular way to create Dockerfiles, and Codefresh supports it, we do**NOT** recommend to write Dockerfiles like this. Please learn about Docker multi-stage builds if you are not familiar with them.
189
189
190
-
You can see this pattern in all kinds ofDockeriles that assume the application is already there (or that dependencies are already downloaded). Here is a[Dockerfile that packages an existing JAR]({{site.baseurl}}/docs/learn-by-example/java/spring-boot-2/#spring-boot-2-and-docker-package-only) file.
190
+
You can see this pattern in all kinds ofDockerfiles that assume the application is already there (or that dependencies are already downloaded). Here is a[Dockerfile that packages an existing JAR]({{site.baseurl}}/docs/learn-by-example/java/spring-boot-2/#spring-boot-2-and-docker-package-only) file.