https://github.com/leplusorg/docker-json
Docker container with utilities to process JSON data (jq, jsonlint...).
https://github.com/leplusorg/docker-json
docker docker-container docker-image dockerfile jason2yaml jose jose-jwt jq json json-manipulation json-schema json-to-yaml json-to-yaml-convertor jsonlint jsonwebtoken jwt jwt-bearer-tokens jwt-token jwt-tokens
Last synced: 27 minutes ago
JSON representation
Docker container with utilities to process JSON data (jq, jsonlint...).
- Host: GitHub
- URL: https://github.com/leplusorg/docker-json
- Owner: leplusorg
- License: apache-2.0
- Created: 2019-12-03T18:35:25.000Z (over 5 years ago)
- Default Branch: main
- Last Pushed: 2025-06-02T17:00:41.000Z (9 days ago)
- Last Synced: 2025-06-03T02:31:33.234Z (8 days ago)
- Topics: docker, docker-container, docker-image, dockerfile, jason2yaml, jose, jose-jwt, jq, json, json-manipulation, json-schema, json-to-yaml, json-to-yaml-convertor, jsonlint, jsonwebtoken, jwt, jwt-bearer-tokens, jwt-token, jwt-tokens
- Language: Dockerfile
- Homepage: https://hub.docker.com/r/leplusorg/json
- Size: 485 KB
- Stars: 6
- Watchers: 2
- Forks: 3
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Security: SECURITY.md
Awesome Lists containing this project
README
# JSON
Multi-platform Docker container with utilities to process JSON data (jq, jsonlint, prettyjson, jose, json2yaml...).
[](json/Dockerfile)
[](https://github.com/leplusorg/docker-json/actions?query=workflow:"Docker")
[](https://hub.docker.com/r/leplusorg/json)
[](https://hub.docker.com/r/leplusorg/json)
[](https://hub.docker.com/r/leplusorg/json)
[](https://bestpractices.coreinfrastructure.org/projects/10070)
[](https://securityscorecards.dev/viewer/?uri=github.com/leplusorg/docker-json)
## Example without using the filesystem
Let's say that you have a file `foo.json` in your current working directory that you want to process with jq:
**Mac/Linux**
```bash
cat foo.json | docker run --rm -i --net=none leplusorg/json jq '.'
```
**Windows**
```batch
type foo.json | docker run --rm -i --net=none leplusorg/json jq '.'
```
## Example using the filesystem
Same thing, assuming that you have a file `foo.json` in your current working directory that you want to process with jq:
**Mac/Linux**
```bash
docker run --rm -t --user="$(id -u):$(id -g)" --net=none -v "$(pwd):/tmp" leplusorg/json jq '.' /tmp/foo.json
```
**Windows**
In `cmd`:
```batch
docker run --rm -t --net=none -v "%cd%:/tmp" leplusorg/json jq '.' /tmp/foo.json
```
In PowerShell:
```pwsh
docker run --rm -t --net=none -v "${PWD}:/tmp" leplusorg/json jq '.' /tmp/foo.json
```
## Help
To know more command-line options of `jq`:
```bash
docker run --rm --net=none leplusorg/json jq -h
```
## Software Bill of Materials (SBOM)
To get the SBOM for the latest image (in SPDX JSON format), use the
following command:
```bash
docker buildx imagetools inspect leplusorg/json --format '{{ json (index .SBOM "linux/amd64").SPDX }}'
```
Replace `linux/amd64` by the desired platform (`linux/amd64`, `linux/arm64` etc.).
### Sigstore
[Sigstore](https://docs.sigstore.dev) is trying to improve supply
chain security by allowing you to verify the origin of an
artifcat. You can verify that the jar that you use was actually
produced by this repository. This means that if you verify the
signature of the ristretto jar, you can trust the integrity of the
whole supply chain from code source, to CI/CD build, to distribution
on Maven Central or whever you got the jar from.
You can use the following command to verify the latest image using its
sigstore signature attestation:
```bash
cosign verify leplusorg/json --certificate-identity-regexp 'https://github\.com/leplusorg/docker-json/\.github/workflows/.+' --certificate-oidc-issuer 'https://token.actions.githubusercontent.com'
```
The output should look something like this:
```text
Verification for index.docker.io/leplusorg/xml:main --
The following checks were performed on each of these signatures:
- The cosign claims were validated
- Existence of the claims in the transparency log was verified offline
- The code-signing certificate was verified using trusted certificate authority certificates
[{"critical":...
```
For instructions on how to install `cosign`, please read this [documentation](https://docs.sigstore.dev/cosign/system_config/installation/).
## Request new tool
Please use [this link](https://github.com/leplusorg/docker-json/issues/new?assignees=thomasleplus&labels=enhancement&template=feature_request.md&title=%5BFEAT%5D) (GitHub account required) to request that a new tool be added to the image. I am always interested in adding new capabilities to these images.