Some fixes in the "Complete workflow example" section

[roipoussiere]

• use the debian:jessie image;
• download curl;
• cd /var/gavo/inputs, otherwise the data are not added to the volume; and gavo can not import them.

Bonus question: I do we use a temp image to add data to the volume ? We can do everything we need with docker exec -it dachs /bin/bash.

[roipoussiere]

I also get this error when importing the q.rd:

with id u'license-cc-by' could not be located in parse context

I need to delete this line on the q.rd file to be able to import the arihip service:

 <FEED source="//procs#license-cc-by" what="ARIHIP"/>

[msdemlei]

+1 to pre-installing curl (but leaving it to carlos to do the merge).

On the license stream: Oh shucks, yes. This is only going in in the 1.0 release of DaCHS, which isn't going to happen before May (and probably a bit later still). I so wanted to document this even in the tutorial that I dumped it in, forgetting that this will break older DaCHSes.

Ah well. I'll fix the arihip thing on my end. Thanks for bringing this to our attention.

[chbrandt]

Hi @roipoussiere , thanks for the fixes.

Answering your question about using a temp image: indeed, we don't need it. The reason I wrote that way was to highlight the ability (and docker feature) to have all elements segmented (data, software).

By all means, Nathanael, I wanted (and still want) to arrive to a setup (docker-dachs images and data volumes) plus workflow where the user could control as most as possible the system from outside (i.e, from the host system, instead of from inside the containers)...That is probably the reason why more-than-necessary images are being called their.

Thanks!