https://bugzilla.redhat.com/show_bug.cgi?id=1213385
--- Comment #9 from Jan Pazdziora <[email protected]> --- I could certainly do something like RUN ... process list of directories to put to volume (== move aside to /data-template during build) ... if [ "$i" == /var/log/ ] ; then mv /var/log /var/log-removed ; else rm -rf $i ; fi ... RUN rm -rf /var/log-removed But why mount it directly to /var/log/journal/... in the first place? Why not something like /run/journal/data and have the /var/log/journal/... be a symlink to it? I assume for many people, having /var/log in a volume is and will be way to go, and preparing for journald support shouldn't break that. I'm scared what other not-so-obvious features might be included in the future. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ golang mailing list [email protected] https://lists.fedoraproject.org/mailman/listinfo/golang
