Hi Bachir,
I’m afraid I’m not much of a help because the whole docker-sharade is new to me.
I did encounter the same problems as you. Can’t say that it is a bug , it is more the combination: OS, docker and BaseX concerning ownership of the mounted docker files.
I got it running by logging in as superuser in the docker container as described in previous mail and running:
This changed the ownership of the file for me.
I also optimized the database-files through the BaseX’s DBA-webapplication.
This is all the help I can get you.
Have fun,
Rob
Sent from Mail for Windows
From: basex-talk-request@mailman.uni-konstanz.de
Sent: Wednesday, December 8, 2021 12:00 PM
To: basex-talk@mailman.uni-konstanz.de
Subject: BaseX-Talk Digest, Vol 144, Issue 4
Send BaseX-Talk mailing list submissions to
basex-talk@mailman.uni-konstanz.de
To subscribe or unsubscribe via the World Wide Web, visit
https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
or, via email, send a message with subject or body 'help' to
basex-talk-request@mailman.uni-konstanz.de
You can reach the person managing the list at
basex-talk-owner@mailman.uni-konstanz.de
When replying, please edit your Subject line so it is more specific
than "Re: Contents of BaseX-Talk digest..."
Today's Topics:
1. reply to 2. docker basexhttp wrong owner of /srv/basex/*
(scbh) (Rob Stapper)
2. Re: reply to 2. docker basexhttp wrong owner of /srv/basex/*
(scbh) (scbh)
----------------------------------------------------------------------
Message: 1
Date: Tue, 7 Dec 2021 12:37:00 +0100
From: Rob Stapper <r.stapper@lijbrandt.nl>
To: "basex-talk@mailman.uni-konstanz.de"
<basex-talk@mailman.uni-konstanz.de>
Subject: [basex-talk] reply to 2. docker basexhttp wrong owner of
/srv/basex/* (scbh)
Message-ID: <fe337fd0-5751-11ec-aee6-005056998788@smtp.kpnmail.nl>
Content-Type: text/plain; charset="utf-8"
Hi Bach,
Login as super-user[1] in your running container to change ownerschip.
[1] docker exec -u 0 -it <myrunningcontainer> bash
Succes,
Rob
Sent from Mail for Windows
--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.uni-konstanz.de/pipermail/basex-talk/attachments/20211207/3fd2cd70/attachment-0001.htm>
------------------------------
Message: 2
Date: Tue, 07 Dec 2021 17:14:49 +0100
From: scbh <sc.bh@free.fr>
To: "basex-talk@mailman.uni-konstanz.de"
<basex-talk@mailman.uni-konstanz.de>
Subject: Re: [basex-talk] reply to 2. docker basexhttp wrong owner of
/srv/basex/* (scbh)
Message-ID: <13326425.RDIVbhacDa@razerblade-arch-bach>
Content-Type: text/plain; charset="iso-8859-1"
Hi Rob,
thanks for the tip
that's what i already do, but far from ideal
is it normal ? a bug ? related to my env ?
i can't figure it out
bach
On mardi 7 d?cembre 2021 12:37:00 CET Rob Stapper wrote:
> Hi Bach,
>
> Login as super-user[1] in your running container to change ownerschip.
>
> [1] docker exec -u 0 -it <myrunningcontainer> bash
>
> Succes,
> Rob
>
> Sent from Mail for Windows
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.uni-konstanz.de/pipermail/basex-talk/attachments/20211207/2daf53d5/attachment-0001.htm>
End of BaseX-Talk Digest, Vol 144, Issue 4
******************************************