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/prokka docker image #165

Merged
merged 3 commits into from
Mar 31, 2022
Merged

Feature/prokka docker image #165

merged 3 commits into from
Mar 31, 2022

Conversation

nkleinbo
Copy link
Collaborator

First version of a custom docker image for prokka with support for partial genes, based on this pull request:

tseemann/prokka#219

Possible optimizations:

  • smaller image size
  • merge the pull request with a newer prokka version, this one does not support tsv output, which we might need

@nkleinbo nkleinbo closed this Mar 24, 2022
@nkleinbo nkleinbo reopened this Mar 24, 2022
@nkleinbo nkleinbo changed the base branch from master to dev March 24, 2022 08:33
@nkleinbo nkleinbo requested review from bosterholz and pbelmann March 24, 2022 11:23

# install dependencies
RUN apt-get update && \
apt-get -y --no-install-recommends install libdatetime-perl libxml-simple-perl libdigest-md5-perl git default-jre bioperl hmmer wget \
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just out of curiosity, do you know which tool needs java (default-jre) ?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one seems to be the only tool that needs java (tool for finding CRISPR elements)
https://github.com/ctSkennerton/minced

@@ -0,0 +1 @@
0.1.0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe we should apply the following versioning scheme to our docker images:
TOOLVERSION_IMAGEVERSION

For example in your case it would be 1.12.0-0. This way its easier to understand which version of a tool is used. If we update our image because we might are able to create a smaller image then we would increment the last number (i.e 1.12.0-1). This would be still compatible with semantic versioning. I believe we should apply this scheme to all of our images, but this would be seperate issue.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've changed the version number in the VERSION file as you suggested.

Copy link
Collaborator

@bosterholz bosterholz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good work. Can be merged after Peters feedback is addressed.

@nkleinbo nkleinbo merged commit 15a90af into dev Mar 31, 2022
@pbelmann pbelmann deleted the feature/prokka_docker_image branch March 31, 2022 07:11
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

Successfully merging this pull request may close these issues.

3 participants