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: CHANGELOG.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -215,13 +215,13 @@ to `Dockerfile.reversed`
215
215
### New Features
216
216
217
217
- Container probe feature to use one of the compose services to test/probe the target container (`--container-probe-compose-svc` flag and `container.probe` continue-after mode)
218
-
- Ability to override the container image name and/or tag when targetting a compose service (`--target-compose-svc-image` flag)
218
+
- Ability to override the container image name and/or tag when targeting a compose service (`--target-compose-svc-image` flag)
219
219
- Ability to wait before executing the HTTP probes (`--http-probe-start-wait` flag)
220
220
- Ability to wait before starting each compose service (`--compose-svc-start-wait` flag)
221
221
- Basic FastCGI protocol support in HTTP probes (docs TBD)
222
222
- New `registry` command and a basic `pull` subcommand
223
223
-`--include-new` build flag to keep new files created by target during dynamic analysis
224
-
-Supprot for stored global param in `slim.config.json`
224
+
-Support for stored global param in `slim.config.json`
Copy file name to clipboardExpand all lines: README.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,7 +76,7 @@ archlinux latest ... ... 467MB
76
76
77
77
## Community
78
78
79
-
Feel free to join any of these channels or just open a new [`Github issue`](https://github.com/slimtoolkit/slim/issues) if you want to chat or if you need help.
79
+
Feel free to join any of these channels or just open a new [`GitHub issue`](https://github.com/slimtoolkit/slim/issues) if you want to chat or if you need help.
Integrating SlimToolkit in Github Actions in your CI/CD workflow involves using the [Docker-Slim Github Action](https://github.com/marketplace/actions/docker-slim-github-action), this Action(snippet below) minifies a target docker image--IMAGE_NAME:latest in your workflow, making it smaller and adjusting the new slimmed image as IMAGE_NAME:slim.
877
+
### Integrating Slimtoolkit in GitHub Actions
878
+
#### GitHub Action
879
+
Integrating SlimToolkit in GitHub Actions in your CI/CD workflow involves using the [Docker-Slim GitHub Action](https://github.com/marketplace/actions/docker-slim-github-action), this Action(snippet below) minifies a target docker image--IMAGE_NAME:latest in your workflow, making it smaller and adjusting the new slimmed image as IMAGE_NAME:slim.
880
880
```
881
881
# Slim it!
882
882
- uses: kitabisa/docker-slim-action@v1
@@ -886,8 +886,8 @@ Integrating SlimToolkit in Github Actions in your CI/CD workflow involves using
886
886
target: IMAGE_NAME:latest
887
887
tag: "slim"
888
888
```
889
-
#### Github Actions Slim Workflow
890
-
You can integrate the Docker-Slim Github Action in your workflow by inserting the Action after a [Docker Build/Push Github Action](https://github.com/docker/build-push-action), before [Docker Login Github Action](https://github.com/docker/login-action) and docker tag/push commands, a customized example workflow is highlighted below. Note that the environment variable tag--{{github.run_number}} in the workflow represents a unique incremental number allocated by Github Actions each time your workflow runs.
889
+
#### GitHub Actions Slim Workflow
890
+
You can integrate the Docker-Slim GitHub Action in your workflow by inserting the Action after a [Docker Build/Push GitHub Action](https://github.com/docker/build-push-action), before [Docker Login GitHub Action](https://github.com/docker/login-action) and docker tag/push commands, a customized example workflow is highlighted below. Note that the environment variable tag--{{github.run_number}} in the workflow represents a unique incremental number allocated by GitHub Actions each time your workflow runs.
891
891
```
892
892
# Build the Docker image first
893
893
- uses: docker/build-push-action@v4
@@ -915,9 +915,9 @@ You can integrate the Docker-Slim Github Action in your workflow by inserting th
- A [Docker Build/Push Github Action](https://github.com/docker/build-push-action) for building a docker image with the image name/tag--IMAGE_NAME:{{github.run_number}}, you should give replace IMAGE_NAME with your desired image name. Note that this Action must have a false option to push the built image--given that you need the image slimmed/minified before pushing it to a container registry.
919
-
- A Docker-Slim Github Action which minifies the target image--IMAGE_NAME:{{github.run_number}}, this Action has the "slim-{{github.run_number}}" tag and adds this tag to the slimmed/minified docker image such that the image name/tag becomes IMAGE_NAME:slim-{{github.run_number}}.
920
-
- A Docker Login Github Action which logs into your DockerHub container regristry account, you should store your DockerHub username and personal access token as secrets in the github repository meant for the workflow. Suppose your container registry is not DockerHub, you can check the [Docker Login Github Action documentation](https://github.com/docker/login-action) for the use case of logging into your desired container registry.
918
+
- A [Docker Build/Push GitHub Action](https://github.com/docker/build-push-action) for building a docker image with the image name/tag--IMAGE_NAME:{{github.run_number}}, you should give replace IMAGE_NAME with your desired image name. Note that this Action must have a false option to push the built image--given that you need the image slimmed/minified before pushing it to a container registry.
919
+
- A Docker-Slim GitHub Action which minifies the target image--IMAGE_NAME:{{github.run_number}}, this Action has the "slim-{{github.run_number}}" tag and adds this tag to the slimmed/minified docker image such that the image name/tag becomes IMAGE_NAME:slim-{{github.run_number}}.
920
+
- A Docker Login GitHub Action which logs into your DockerHub container regristry account, you should store your DockerHub username and personal access token as secrets in the github repository meant for the workflow. Suppose your container registry is not DockerHub, you can check the [Docker Login GitHub Action documentation](https://github.com/docker/login-action) for the use case of logging into your desired container registry.
921
921
- A docker tag command for naming/tagging the slimmed image with your DockerHub account remote repository name which could be the same name(IMAGE_NAME) as the slimmed image; A docker push command to push the slimmed image to your Dockerhub account remote repository.
922
922
923
923
@@ -1011,7 +1011,7 @@ Commands in `probeCmds.json`:
1011
1011
"resource": "/submit"
1012
1012
},
1013
1013
{
1014
-
"procotol": "http",
1014
+
"protocol": "http",
1015
1015
"resource": "/api/call?arg=one"
1016
1016
},
1017
1017
{
@@ -1415,7 +1415,7 @@ DockerSlim was a `Docker Global Hack Day` \#`dockerhackday` project. It barely w
Since then it's been improved and it works pretty well for its core use cases. It can be better though. That's why the project needs your help! You don't need to know much about the container internals, container runtimes and you don't need to know anything about Go. You can contribute in many different ways. For example, use Slim on your images and open Github issues documenting your experience even if it worked just fine :-)
1418
+
Since then it's been improved and it works pretty well for its core use cases. It can be better though. That's why the project needs your help! You don't need to know much about the container internals, container runtimes and you don't need to know anything about Go. You can contribute in many different ways. For example, use Slim on your images and open GitHub issues documenting your experience even if it worked just fine :-)
Copy file name to clipboardExpand all lines: pkg/app/master/command/build/flags.go
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -148,7 +148,7 @@ const (
148
148
FlagCBONetwork="cbo-network"
149
149
FlagCBOCacheFrom="cbo-cache-from"
150
150
151
-
//Experimenal flags
151
+
//Experimental flags
152
152
FlagObfuscateMetadata="obfuscate-metadata"
153
153
)
154
154
@@ -163,7 +163,7 @@ const (
163
163
164
164
FlagPathPermsUsage="Set path permissions in optimized image"
165
165
FlagPathPermsFileUsage="File with path permissions to set"
166
-
FlagPreservePathUsage="Keep path from orignal image in its initial state (changes to the selected container image files when it runs will be discarded)"
166
+
FlagPreservePathUsage="Keep path from original image in its initial state (changes to the selected container image files when it runs will be discarded)"
167
167
FlagPreservePathFileUsage="File with paths to keep from original image in their original state (changes to the selected container image files when it runs will be discarded)"
168
168
FlagIncludePathUsage="Keep path from original image"
169
169
FlagIncludePathFileUsage="File with paths to keep from original image"
0 commit comments