Remi Rampin

Hi and thanks for looking into this! Basically the semantics I want: * Copy the files from the TAR into the image (with UNIX permissions/ownership) * Replace existing files with...

I think the best solution for both of us is to write out a Docker container TAR directly for `docker import`, you by going through the config file and copying...

Also note that being able to trace Docker images is something we are interested in! Tracing without installing ReproZip inside the container should be possible (but not super straightforward). I...

The processes in the container's PID namespace also exist as processes on the host, so you can attach to them from the outside. However you would need the application to...

Also note that if using things like docker-machine or "docker native" the "host" is the VM, which would make this a bit annoying (unless ReproZip is also running in a...

I think `ADD` didn't behave properly when the permissions for directories differ between the tar and the container, and when the same path is a file and a directory. Also...

Hi @kaczmarj, unfortunately I have no code for this yet. This would be a change in the beginning of the tracer (instead of current `fork_and_trace()`) + some wrapper for the...

I will look into it. Do you think it would be possible to use a "reprounzip" docker image as the other container, so that anyone can build a Docker image...

(duplicates #34) There is no work yet on OS X support. The ptrace facility we use on Linux is not available on OS X, so the tracing part would have...

> a colleague had created this injectable library: https://github.com/vladistan/ProvTrace/tree/master/Mac An injectable library might be good enough, but for the kind of provenance we want, dtrace might be easier. It looks...