Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix minor typos #336

Merged
merged 1 commit into from
Dec 4, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion .github/dependabot.yml
Original file line number Diff line number Diff line change
Expand Up @@ -10,4 +10,3 @@ updates:
directory: "/"
schedule:
interval: weekly

1 change: 1 addition & 0 deletions .markdownlint.yaml
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
---
default: true
MD004: false
MD012: false
Expand Down
8 changes: 4 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -320,14 +320,14 @@ provided. Any valid instruction will work, including `MAINTAINER`,

This should be used as little as possible.

#### Exemple use case of intermediate_instruction
#### Example use case of intermediate_instruction

A possible use case is running kitchen behind a [MITM proxy](https://en.wikipedia.org/wiki/Man-in-the-middle_attack)
If you did read the link, it's scary yes, but a reality in many corporate networks where any HTTPS connection is intercepted, when done right (morally) the proxy uses an internal Certificate Authority (CA) which is not trusted by most programs.

It's always a problem to get things accessing TLS secured servers through this kind of proxy when working in a container and here is how you can do it for Chef specifically.

Using kitchen `intemediate_instructions` and `entrypoint` you can overcome the problem in dokken in this way:
Using kitchen `intermediate_instructions` and `entrypoint` you can overcome the problem in dokken in this way:

```yaml
driver:
Expand Down Expand Up @@ -414,7 +414,7 @@ On some versions of Ubuntu (16.04 at least), the container deletes all the downl
driver:
name: dokken
volumes:
# saves the apt archieves outside of the container
# saves the apt archives outside of the container
- /var/cache/apt/archives/:/var/cache/apt/archives/

platforms:
Expand Down Expand Up @@ -608,7 +608,7 @@ To allow IPv6 Docker networks to reach the internet IPv6 firewall rules must be
}
```

Some containers require the `ip6table_filter` kernel module to be loaded on the host system or ip6tables will not dunction on the container (Centos 7 for example). To check if the module is loaded use the command
Some containers require the `ip6table_filter` kernel module to be loaded on the host system or ip6tables will not function on the container (Centos 7 for example). To check if the module is loaded use the command

```shell
sudo lsmod | grep ip6table_filter
Expand Down
2 changes: 1 addition & 1 deletion lib/kitchen/transport/dokken.rb
Original file line number Diff line number Diff line change
Expand Up @@ -247,7 +247,7 @@ def connection_options(data)
# Creates a new Dokken Connection instance and save it for potential future
# reuse.
#
# @param options [Hash] conneciton options
# @param options [Hash] connection options
# @return [Ssh::Connection] an SSH Connection instance
# @api private
def create_new_connection(options, &block)
Expand Down
Loading