thrift pulls statistics

DEPRECATION NOTICE

This image is deprecated due to inactivity (last updated Feb 2019; docker-library/official-images#5411).

There is a useful discussion in ahawkins/docker-thrift#12 about the future of this image.

Quick reference

• Maintained by:
  the Docker Community

• Where to get help:
  the Docker Community Forums, the Docker Community Slack, or Stack Overflow

Supported tags and respective Dockerfile links

• 0.9, 0.9.3
• 0.10, 0.10.0
• 0.11, 0.11.0
• 0.12, 0.12.0, latest

Quick reference (cont.)

• Where to file issues:
  https://github.com/ahawkins/docker-thrift/issues

• Supported architectures: (more info)
  amd64

• Published image artifact details:
  repo-info repo's repos/thrift/ directory (history)
  (image metadata, transfer size, etc)

• Image updates:
  official-images repo's library/thrift label
  official-images repo's library/thrift file (history)

• Source of this description:
  docs repo's thrift/ directory (history)

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.