Latest release of SQLite3 container. (Alpine base with AMD and Arm support)
1M+
Alpine Docker image of SQLite3 built from the latest source code.
docker pull keinos/sqlite3:latest
INIT Support:
Repositories/Registries:
Build Info:
alpine:latestBasic Vulnerability Scan:
Verification of Image Signature Using Cosign:
As of 3.50.4, the image is signed using Cosign. Check if the result contains "The cosign claims were validated". (See issue #86 and #88)
# get digest
DIGEST=$(docker buildx imagetools inspect "docker.io/keinos/sqlite3:latest" --format '{{json .}}' | jq -r '.manifest.digest')
# verify
cosign verify \
--certificate-identity 'https://github.com/KEINOS/Dockerfile_of_SQLite3/.github/workflows/deploy-on-merge.yml@refs/heads/master' \
--certificate-oidc-issuer 'https://token.actions.githubusercontent.com' \
"docker.io/keinos/sqlite3@${DIGEST}"
SBOM
$ docker sbom keinos/sqlite3:latest
Syft v0.43.0
✔ Loaded image
✔ Parsed image
✔ Cataloged packages [14 packages]
NAME VERSION TYPE
alpine-baselayout 3.6.5-r0 apk
alpine-baselayout-data 3.6.5-r0 apk
alpine-keys 2.4-r1 apk
apk-tools 2.14.4-r0 apk
busybox 1.36.1-r29 apk
busybox-binsh 1.36.1-r29 apk
ca-certificates-bundle 20240226-r0 apk
libcrypto3 3.3.1-r0 apk
libssl3 3.3.1-r0 apk
musl 1.2.5-r0 apk
musl-utils 1.2.5-r0 apk
scanelf 1.3.7-r2 apk
ssl_client 1.36.1-r29 apk
zlib 1.3.1-r1 apk
$ docker pull keinos/sqlite3:latest
**snip**
$ docker pull keinos/sqlite3:3.44.2
...
$ docker build -t sqlite3:local https://github.com/KEINOS/Dockerfile_of_SQLite3.git
...
Running sqlite3 command inside the container interactively.
$ docker run --rm -it -v "$(pwd):/workspace" -w /workspace keinos/sqlite3
SQLite version 3.28.0 2019-04-16 19:49:53
Enter ".help" for usage hints.
Connected to a transient in-memory database.
Use ".open FILENAME" to reopen on a persistent database.
sqlite> .open ./sample.db
sqlite> CREATE TABLE table_sample(timestamp TEXT, description TEXT);
sqlite> INSERT INTO table_sample VALUES(datetime('now'),'First sample data. Foo');
sqlite> INSERT INTO table_sample VALUES(datetime('now'),'Second sample data. Bar');
sqlite> .quit
$ ls
sample.db
sqlite3 --version command:$ docker run --rm keinos/sqlite3 sqlite3 --version
3.38.2 2022-03-26 13:51:10 d33c709cc0af66bc5b6dc6216eba9f1f0b40960b9ae83694c986fbf4c1d6f08f
$ ls
sample.db
$ docker run --rm -it -v "$(pwd):/workspace" keinos/sqlite3 sqlite3 /workspace/sample.db -header -column 'SELECT rowid, * FROM table_sample;'
rowid timestamp description
----- ------------------- -----------------------
1 2022-04-16 14:09:52 First sample data. Foo
2 2022-04-16 14:09:58 Second sample data. Bar
This container includes a simple test script.
You can run the script to see if the container and sqlite3 binary is working. Though, not sutiable for HEALTHCHECK usage.
$ docker run --rm keinos/sqlite3 /run-test.sh
- Creating test DB ... created
rowid timestamp description
----- ------------------- -----------------------
1 2022-04-16 14:18:34 First sample data. Hoo
2 2022-04-16 14:18:34 Second sample data. Bar
- Testing ...
1st row value ... OK
2nd row value ... OK
- Test result:
success
$ echo $?
0
If your image is based on alpine, you can copy the sqlite3 binary from this image as below.
FROM keinos/sqlite3:latest AS sqlite3
FROM alpine:latest
COPY --from=sqlite3 /usr/bin/sqlite3 /usr/bin/sqlite3
ENV \
USER_SQLITE=sqlite \
GROUP_SQLITE=sqlite
RUN \
addgroup -S $GROUP_SQLITE && \
adduser -S $USER_SQLITE -G $GROUP_SQLITE
... do whatever you want ...
Content type
Image
Digest
sha256:a5610a155…
Size
4.3 MB
Last updated
about 2 months ago
docker pull keinos/sqlite3