aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorRob Austein <sra@hactrn.net>2019-02-11 22:17:44 +0000
committerRob Austein <sra@hactrn.net>2019-02-11 22:17:44 +0000
commit8b18f65526d2b600c4aef49be338a83402bb6b58 (patch)
tree439b4a893d181bddde48ae7031afc3c0285ac11e /README.md
parent2fb10e93039defa73810140fb10bef1ab23650c4 (diff)
Update notes.
Diffstat (limited to 'README.md')
-rw-r--r--README.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/README.md b/README.md
index cf7c8c5..1d9e25c 100644
--- a/README.md
+++ b/README.md
@@ -153,3 +153,13 @@ even need to convert from `xwd` format to something more common, we
can just `shutil.copyfile()` the frame buffer file and leave the
results for somebody else to deal with. If anything is going to keep
those they should probably be converted to png but not critical.
+
+OK, confirmed that the problem with running `Xvfb` is (somehow)
+specific to running under `docker build`. Same configuration (packge
+list, etc) ran (apparently) fine under `docker run`.
+
+Attempting to `docker commit` the result blew out what was left of my
+disk space. Since we're going to want to clean up and collapse
+anyway, it's possible that `docker container export` is a better path
+than commit here: would have to feed the result to `docker import` to
+get an image, but that might be exactly what we want.