issues
search
nuest
/
ten-simple-rules-dockerfiles
Ten Simple Rules for Writing Dockerfiles for Reproducible Data Science
https://doi.org/10.1371/journal.pcbi.1008316
Creative Commons Attribution 4.0 International
61
stars
15
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
cleaning up introduction and removing content that goes off track
#57
vsoch
closed
4 years ago
1
Invite feedback
#56
nuest
closed
4 years ago
4
Add note about audience for paper to introduction
#55
vsoch
closed
4 years ago
6
Stephen's edits
#54
sje30
closed
4 years ago
5
Acknowledgements
#53
nuest
closed
4 years ago
4
Multiple images vs. one image with entrypoints/cmds
#52
nuest
closed
4 years ago
4
Preprint venue
#51
nuest
closed
4 years ago
16
ContainDS
#50
nuest
closed
4 years ago
9
related work
#49
mr-c
closed
4 years ago
7
Ben's edits to the text
#48
benmarwick
closed
4 years ago
5
Rule2 typos clarification
#47
psychemedia
closed
4 years ago
0
update rule 7, closes #41 #14
#46
nuest
closed
4 years ago
0
Typos
#45
psychemedia
closed
4 years ago
0
"simply pushing the `Dockerfile` to the service"
#44
psychemedia
closed
4 years ago
9
"the harder it will become"
#43
psychemedia
closed
4 years ago
1
"a tool like `docker-compose`"
#42
psychemedia
closed
4 years ago
1
"`x11` support, `x11docker` is recommended"
#41
psychemedia
closed
4 years ago
6
"you should consider switching tools"
#40
psychemedia
closed
4 years ago
2
"a private dataset ... should never be added to a container"
#39
psychemedia
closed
4 years ago
0
"in the case that you will likely save as a root user"
#38
psychemedia
closed
4 years ago
1
"small data files and software that is essential for the function of a container"
#37
psychemedia
closed
4 years ago
3
"Package managers generally provide reliable mirrors"
#36
psychemedia
closed
4 years ago
0
"You should list commands"
#35
psychemedia
closed
4 years ago
0
"try to design the `RUN` statements"
#34
psychemedia
closed
4 years ago
1
Formatting Dockerfiles
#33
psychemedia
closed
4 years ago
2
"A tag like `latest` "
#32
psychemedia
closed
4 years ago
0
"configure an automated build"
#31
psychemedia
closed
4 years ago
1
"maintained by the Docker library"
#30
psychemedia
closed
4 years ago
1
Optimising container for use
#29
psychemedia
closed
4 years ago
5
Reusing / extending a Dockerfile
#28
psychemedia
closed
4 years ago
4
Platforms docker containers are tested on
#27
psychemedia
closed
4 years ago
11
Reuse and reproducibility in other build environments
#26
psychemedia
closed
4 years ago
2
portabal -> portable
#25
vsoch
closed
4 years ago
1
Final check of form
#24
nuest
closed
4 years ago
2
Author summary and/or abstract
#23
nuest
closed
4 years ago
1
Good Points
#22
vsoch
closed
4 years ago
6
Updates by @vsoch
#21
vsoch
closed
4 years ago
5
Add Dockerfile
#20
vsoch
closed
4 years ago
3
Paper Build not Reproducible
#19
vsoch
closed
4 years ago
5
Unaddressed issues
#18
psychemedia
closed
4 years ago
14
Discussion - Rule 10. Use the container daily, rebuild the image weekly
#17
psychemedia
closed
4 years ago
6
Disussion - Rule 9. Publish a Dockerfile per project in a code repository with version control
#16
psychemedia
closed
4 years ago
7
Disussion - Rule 8. End the `Dockerfile` with build and run commands
#15
psychemedia
closed
4 years ago
2
Discussion - Rule 7. Enable interactive usage and one-click execution
#14
psychemedia
closed
4 years ago
1
Discussion - Rule 6. Capture environment metadata
#13
psychemedia
closed
4 years ago
1
Discussion - Rule 5. Mount data and control code
#12
psychemedia
closed
4 years ago
0
Discussion - Rule 4. Pin versions
#11
psychemedia
closed
4 years ago
1
Discussion - Rule 3. Use formatting and favour clarity
#10
psychemedia
closed
4 years ago
2
Discussion: Rule 2. Use versioned and automatically built base images
#9
psychemedia
closed
4 years ago
4
Discussion: Rule 1 - Don't write Dockerfiles by hand
#8
psychemedia
closed
4 years ago
19
Previous
Next