On Tue, 19 Nov 2019 at 12:26, sebb <seb...@gmail.com> wrote:

> docker:update had issues pulling down various svn repos, e.g.
>
> svn: E170013: Unable to connect to a repository at URL  ...
> svn: E125009: Invalid config: unable to load certificate file
> '/Users/sebb/.subversion/Thawte_Premium_Server_CA.pem'
>
> I was able to remove the Invalid config error by changing /Users/sebb =>
> /root
> However I then got the error:
>
> svn: E000111: Error running context: Connection refused
>
> I assume that is because my SVN is set to grab passwords from the macOS
> keychain
>
>
Turns out that SVN was down at the time.

Once I copied the cert to the expected place it worked OK.

I've just realised that the /srv/svn directory is mounted from the host OS.
So checkouts in the image actually update the host working directory.
Given that, it seems to me it would make more sense to do the check-out on
the host under /srv, and mount that instead.

Also there does not seem to be a visual editor included in the docker build.
> (I had to use sed)
> It would be useful to have vi(m) or such.
>
> S.
> On Tue, 19 Nov 2019 at 03:24, Sam Ruby <ru...@intertwingly.net> wrote:
>
>> On Sat, Oct 19, 2019 at 12:43 AM Dave Fisher <wave4d...@comcast.net>
>> wrote:
>> >
>> > Maybe a docker image is the way to go. I’ll test it if you point it out.
>>
>> Beta testers wanted:
>> https://github.com/apache/whimsy/blob/master/DOCKER.md
>>
>> - Sam Ruby
>>
>

Reply via email to