HELP on setting AMP in a docker container

  • 454 Views
  • Last Post 07 June 2019
Altheran posted this 04 June 2019

Hi, I have an UNRAID server.

Want (need) to run AMP inside a docker container.

Tried many containers, the latest and most recently updated being : https://github.com/spritsail/amp-minecraft

docker run -d --name='AMP' --net='eth0' --ip='192.168.1.xxx' -e TZ="America/NewYork" -e HOSTOS="Unraid" -e 'LICENCE'='licence I received by mail (Full Pro)' -e 'USERNAME'='xxxxx' -e 'PASSWORD'='xxxxxxxx' -e 'MODULE'='Minecraft' -v '/mnt/user/appdata/docker_data/AMP':'/ampdata':'rw' 'spritsail/amp-minecraft'

It fails to start and logs give me this :

/opt/amp/ampinstmgr
[Info] AMP Instance Manager v1.6.10.2 built 10/09/2018 17:16
[00:23:27] [Core Info] ???????????: Starting AMP version 1.8.0.2 (TITAN), built 22/05/2019 10:44

[00:23:27] [Core Info] ???????????: Release spec: Release - built by CUBECODERS/BuildBot on CCL-DEV
[00:23:27] [Core Info] ???????????: Running in a Docker environment.
[00:23:27] [Core Info] ???????????: OS: Linux / x86_64
[00:23:27] [Core Info] ???????????: CPU: Intel(R) Xeon(R) CPU E3-1245 v5 @ 3.50GHz (4C/8T)

[00:23:27] [Core Info] ???????????: AMP Instance ID: redacted
[00:23:27] [Core Info] ???????????: Checking for AMP updates...
[00:23:27] [WebServer Info] ??????: Websockets are enabled.
[00:23:27] [ModuleLoader Info] ???: Loaded MinecraftModule version 1.0.0.3 by CubeCoders Limited

[00:23:27] [ModuleLoader Info] ???: Loaded FileManager version 1.0.0.0 by CubeCoders Limited

[00:23:27] [ModuleLoader Info] ???: Loaded EmailSender version 1.0.0.0 by CubeCoders Limited

[00:23:27] [ModuleLoader Info] ???: Loaded PushBulletPlugin version 1.0.0.0 by CubeCoders Limited

[00:23:27] [ModuleLoader Info] ???: Loaded LocalFileBackupPlugin version 1.0.0.0 by CubeCoders Limited

[00:23:27] [Core Info] ???????????: Performing activation, please wait...
[00:23:27] [Minecraft Warning] ???: Unable to get Spigot version data from https://hub.spigotmc.org/versions/: Error: TrustFailure (A call to SSPI failed, see inner exception.)

[00:23:28] [Core:Activation Error] : Couldn't activate: Error: TrustFailure (A call to SSPI failed, see inner exception.)

[00:23:28] [Core:Activation Error] : A call to SSPI failed, see inner exception.

[00:23:28] [Core Info] ???????????: Failed to activate: Module Shared.Action Result`1[CCL Client45.Licencing+Activation Result]

[00:23:28] [Core Info] ???????????: -configonly specified or activation performed. Saving settings and shutting down.
[00:23:28] [Core Info] ???????????: Starting AMP version 1.8.0.2 (TITAN), built 22/05/2019 10:44

[00:23:28] [Core Info] ???????????: Release spec: Release - built by CUBECODERS/BuildBot on CCL-DEV
[00:23:28] [Core Info] ???????????: Running in a Docker environment.
[00:23:28] [Core Info] ???????????: OS: Linux / x86_64
[00:23:28] [Core Info] ???????????: CPU: Intel(R) Xeon(R) CPU E3-1245 v5 @ 3.50GHz (4C/8T)

[00:23:28] [Core Info] ???????????: AMP Instance ID: redacted
[00:23:28] [Core Info] ???????????: Checking for AMP updates...
[00:23:28] [WebServer Info] ??????: Websockets are enabled.
[00:23:28] [ModuleLoader Info] ???: Loaded MinecraftModule version 1.0.0.3 by CubeCoders Limited

[00:23:28] [ModuleLoader Info] ???: Loaded FileManager version 1.0.0.0 by CubeCoders Limited

[00:23:28] [ModuleLoader Info] ???: Loaded EmailSender version 1.0.0.0 by CubeCoders Limited

[00:23:28] [ModuleLoader Info] ???: Loaded PushBulletPlugin version 1.0.0.0 by CubeCoders Limited

[00:23:28] [ModuleLoader Info] ???: Loaded LocalFileBackupPlugin version 1.0.0.0 by CubeCoders Limited

[00:23:29] [Core Error] ??????????: AMP may not run without a licence.

So um .... help ?

I would not care to use an official Cubecoders Container ... but the two I found I Terribly lacking in documentation and doesn't seem to work in any similar fashion to any of the other containers.

Order By: Standard | Newest | Votes
Mike posted this 04 June 2019

We can't offer any support for unofficial containers. You should contact whoever put that docker file together. The official containers are for use by ampinstmgr only and cannot be deployed without it.

Altheran posted this 04 June 2019

We can't offer any support for unofficial containers. You should contact whoever put that docker file together. The official containers are for use by ampinstmgr only and cannot be deployed without it.

Alright then, how do I use ampinstmgr on Unraid ? (Slackware based)

Mike posted this 04 June 2019

For Unraid I'd recommend just spinning up a Debian/Ubuntu Server VM and installing AMP inside there. There's been zero testing on Unraid or Slackware.

Altheran posted this 04 June 2019

I find spawning a full OS for a single application quite wasteful.

I hope you understand as a group that developing AMP (ampinstmgr + amp) for Linux as a fully automated docker container would make it so you need to maintain only one release abstracting any other OS limitations or specificity.

I suggest you reach out to the great guys @ Linux server.io. They have made many containers for the most popular apps out there and would definitely help in giving much visibility to your software.

Mike posted this 04 June 2019

The problem with Docker is it cannot handle the situation where you don't know ahead of time what ports you want to open very well. ampinstmgr can get around this by explicitly opening ports because it knows what ports are going to get used at runtime - but without that tool then a dockerfile would need writing for every supported module separately to expose the appropriate ports. It's also difficult to have an instance running inside a container that can safely create new containers itself.

Altheran posted this 06 June 2019

The problem with Docker is it cannot handle the situation where you don't know ahead of time what ports you want to open very well. ampinstmgr can get around this by explicitly opening ports because it knows what ports are going to get used at runtime - but without that tool then a dockerfile would need writing for every supported module separately to expose the appropriate ports. It's also difficult to have an instance running inside a container that can safely create new containers itself.

Example :

run -d --name='ombi' --net='eth0' --ip='192.168.1.222' -e TZ="America/NewYork" -e HOSTOS="Unraid" -e 'PUID'='xxxx' -e 'PGID'='xxx' -v '/mnt/user/appdata/docker_data/ombi':'/config':'rw' 'linuxserver/ombi:latest'

Custom Interface with it's own IP

I don't need to specify ports, it's as if it's in host mode.

Also ... could be running as Host

Also ... could be running as priviledged to pass commands to the host docker engine ? (not quite secure)

You could also pass Environment variables to specify ports that need openning / Module used, that's whate these 3rd party were doing for minecraft before it stoped working. It had an ENVIRONMENT variable 'MODULE'="Minecraft" to pre-determine that module that you wanted to use was Minecraft for exemple.

As for spawning apps dockers, you could pass a docker.sock and have your own docker-engine installed in the master container.

Not much problems, only solutions ;)

Mike posted this 06 June 2019

Oh it can definitely be done, but since Unraid isn't a supported platform at this time it's not something we're working on just yet. As of right now only bare metal and VPSs are supported.

Joly0 posted this 07 June 2019

What about my Docker Container, i think, its the most recent updated one you can find, spritsails ones is definitly "outdated".

https:/ /hub.docker.com/r/joly0/amp

I am going to work on this in the Future, but for the moment, i have to do other things.

Close