thrift
Estimated reading time: 2 minutesThrift is a framework for generating client and services from an IDL.
GitHub repo: https://github.com/ahawkins/docker-thrift
Library reference
This content is imported from the official Docker Library docs, and is provided by the original uploader. You can view the Docker Hub page for this image at https://hub.docker.com/images/thrift
Supported tags and respective Dockerfile
links
0.9
,0.9.3
(0.9/Dockerfile)0.10
,0.10.0
(0.10/Dockerfile)0.11
,0.11.0
(0.11/Dockerfile)0.12
,0.12.0
,latest
(0.12/Dockerfile)
Quick reference
-
Where to get help:
the Docker Community Forums, the Docker Community Slack, or Stack Overflow -
Where to file issues:
https://github.com/ahawkins/docker-thrift/issues -
Maintained by:
the Docker Community -
Published image artifact details:
repo-info repo’srepos/thrift/
directory (history)
(image metadata, transfer size, etc) -
Image updates:
official-images PRs with labellibrary/thrift
official-images repo’slibrary/thrift
file (history) -
Source of this description:
docs repo’sthrift/
directory (history) -
Supported Docker versions:
the latest release (down to 1.6 on a best-effort basis)
What Is Thrift
The Apache Thrift software framework, for scalable cross-language services development, combines a software stack with a code generation engine to build services that work efficiently and seamlessly between C++, Java, Python, PHP, Ruby, Erlang, Perl, Haskell, C#, Cocoa, JavaScript, Node.js, Smalltalk, OCaml and Delphi and other languages.
Read more about Thrift.
How To Use This Image
This is image is intended to run as an executable. Files are provided by mounting a directory. Here’s an example of compiling service.thrift
to ruby to the current directory.
$ docker run -v "$PWD:/data" thrift thrift -o /data --gen rb /data/service.thrift
Note, that you may want to include -u $(id -u)
to set the UID on generated files. The thrift process runs as root by default which will generate root owned files depending on your docker setup.
License
View license information for the software contained in this image.
As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).
Some additional license information which was able to be auto-detected might be found in the repo-info
repository’s thrift/
directory.
As for any pre-built image usage, it is the image user’s responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.