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

Feature Request: Add tags for older releases of PF_Ring #7

Open
jmwample opened this issue Nov 10, 2021 · 1 comment
Open

Feature Request: Add tags for older releases of PF_Ring #7

jmwample opened this issue Nov 10, 2021 · 1 comment

Comments

@jmwample
Copy link

Per the documentation using pfring in docker requires that the version installed on the host is the same as that installed on the container. The containers released here continually update to follow whatever version is the latest with the ubuntu 20.04 apt package. This is an issue because licensing is (relatively) static and packages installed on the host are placed in packaging holds to prevent updates.

This means that:

  1. these containers may suddenly stop working for a host on rebuild when the packaged release versions updates.
  2. hosts with an older version (even a previously packaged release like 7.8.0) cannot support containers without updating licenses or installing from source in their Dockerfile.

It would be great to have tags in the docker releases with the version of pfring in order to support containers for older pfring releases. (i.e. ntop/pfring:8.0.0-ubuntu, ntop/pfring:7.8.0-ubuntu, ntop/pfring:7.6.0-ubuntu, etc)

@jmwample
Copy link
Author

update - as an example (and for my own use) I have built some of the recent releases from source with ubuntu as the base docker image. Would love to see something like this in the official dockerhub repo. I may also update this again if I can figure out the dpkg-buildpackage system.

https://hub.docker.com/r/jmwample/pfring

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant