from what I gather, the link command is deprecated:

 it sounds like you are using the link feature. This has been
deprecated for years. instead, use a   v2 or v3 docker-compose.yml
file (if using compose) or if using a different system, simply put
both containers on the same        │

so the documentation is out of date.

On 9/3/20, Christian Grün <christian.gruen@gmail.com> wrote:
> Hi Nicholas,
>
> Have you already worked through the Docker documentation in our Wiki [1]?
>
> Best,
> Christian
>
> [1] https://docs.basex.org/wiki/Docker
>
>
>
>
> On Thu, Sep 3, 2020 at 4:23 PM Nicholas Saunders
> <saunders.nicholas@gmail.com> wrote:
>>
>> I've just opened an issue:
>>
>> https://github.com/BaseXdb/basex/issues/1936
>>
>> based on an inability to run the docker image:
>>
>> https://devops.stackexchange.com/q/12338/23443
>>
>>
>> but thought I'd ask here if there might be something obvious.  I'm
>> creating the container from the hub image with:
>>
>> docker run -d \
>>     --name basexhttp \
>>     --publish 1984:1984 \
>>     --publish 8984:8984 \
>>     --volume "$HOME/basex/data":/srv/basex/data \
>>     --volume "$HOME/basex/repo":/srv/basex/repo \
>>     --volume "$HOME/basex/webapp":/srv/basex/webapp \
>>     basex/basexhttp:latest
>>
>>
>> and another person reported the missing file.  Is the file missing?
>> I'm not sure.
>