# Issues installing mender server

**URL:** <https://hub.mender.io/t/issues-installing-mender-server/5959>\
**Category:** General Discussions\
**Tags:** mender-server\
**Created:** [June 28, 2023, 2:11pm UTC](https://hub.mender.io/t/issues-installing-mender-server/5959 "2023-06-28T14:11:15Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jjbrock1](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/jjbrock1/32/1935_2.png) [@jjbrock1](https://hub.mender.io/u/jjbrock1)\
**Post date:** [June 28, 2023, 2:11pm UTC](https://hub.mender.io/t/issues-installing-mender-server/5959/1 "2023-06-28T14:11:15Z")

</div>

Hi - I’m taking the (free) mender server for a test spin, and followed the instructions here:  
[https://docs.mender.io/3.4/server-installation/installation-with-docker-compose](https://docs.mender.io/3.4/server-installation/installation-with-docker-compose)

I hit three issues:

1. ./run pull produced these errors

[root@jjbinstance production]# ./run pull  
ERROR: Unsupported major version: 13  
ERROR: Docker Engine must be on version 1.11 or larger, but found version 1.13 installed.  
DOCKER\_ENGINE\_VERSION\_STRING=Server Version: 1.13.1

[root@jjbinstance production]# docker --version  
Docker version 1.13.1, build 7d71120/1.13.1

The verify-docker-versions script seems plain wrong.  
The shell function compare\_versions expects the major version as $1 yet the minor version is passed  
to it.

compare\_versions “$DOCKER\_ENGINE\_VERSION\_MINOR” “$VERSION\_MINOR\_MIN\_DOCKER\_ENGINE”

I hacked the script to be able to proceed.

1. After setting up keys, the Mender documentation says config/prod.yaml should look like:

In my case the config file is different. Specifically, DEPLOYMENTS\_AWS\_EXTERNAL\_URI was set rather than DEPLOYMENTS\_AWS\_URI. DEPLOYMENTS\_AWS\_URI was unchanged. Is the documentation out of date, or is my config incorrect?

```
   environment:
        STORAGE_BACKEND_CERT: /etc/ssl/certs/docker.mender.io.crt
        # access key, the same value as MINIO_ACCESS_KEY
        DEPLOYMENTS_AWS_AUTH_KEY: mender-deployments
        # secret, the same valie as MINIO_SECRET_KEY
        DEPLOYMENTS_AWS_AUTH_SECRET: xxxxxxxxxxxxxxxx

        # deployments service uses signed URLs, hence it needs to access
        # storage-proxy using exactly the same name as devices will; if
        # devices will access storage using https://s3.acme.org, then
        # set this to https://s3.acme.org
        DEPLOYMENTS_AWS_EXTERNAL_URI: https://storage.mender.brockman.tech
        DEPLOYMENTS_AWS_URI: http://minio:9000

```

1. The Mender documentation says:

ERROR: for menderproduction\_mender-useradm\_1 Cannot create container for service mender-useradm: unknown log opt ‘max-size’ for journald log driver  
Creating menderproduction\_mender-workflows-worker\_1 …

It’s not really a Mender issue, but you may want to alert customers to this in the install doc.