I found the solution to fix this problem for minecraft instances with docker. usr/bin/docker: invalid publish opts format (should be name=value but got '8081:8081/tcp'). Run 'ampinstmgr LastLog Minecraft01' to view it's most recent log.ĭocker output: /usr/bin/docker run -rm -d -mac-address 02:42:ac:ff:21:50 -name AMP_Minecraft01 -v "/home/amp/.ampdata/instances/Minecraft01":/AMP -v "/home/amp/.config":/home/amp/.config:ro -v /opt/cubecoders/amp:/opt/cubecoders/amp:ro -p 8081:8081/tcp -e MONO_THREADS_PER_CPU='2000' -e MONO_GC_PARAMS='major=marksweep-conc' -e LD_LIBRARY_PATH='./:/opt/cubecoders/amp/:/AMP/' -e MONO_TLS_PROVIDER='btls' -e LANG='en_US.UTF-8' -e AMPUSERID='1003' -p 25565:25565/both cubecoders/ampbase:java8 Running command line: "/usr/bin/docker run -rm -d -mac-address 02:42:ac:ff:21:50 -name AMP_Minecraft01 -v "/home/amp/.ampdata/instances/Minecraft01":/AMP -v "/home/amp/.config":/home/amp/.config:ro -v /opt/cubecoders/amp:/opt/cubecoders/amp:ro -p 8081:8081/tcp -e MONO_THREADS_PER_CPU='2000' -e MONO_GC_PARAMS='major=marksweep-conc' -e LD_LIBRARY_PATH='./:/opt/cubecoders/amp/:/AMP/' -e MONO_TLS_PROVIDER='btls' -e LANG='en_US.UTF-8' -e AMPUSERID='1003' -p 25565:25565/both cubecoders/ampbase:java8" from "" Arguments: images cubecoders/ampbase -format
Running command line: "/usr/bin/docker inspect AMP_Minecraft01" from "" Loading instances from /home/amp/.ampdata/instances.json. Current certificate store contains 128 items, system store contains 128 Syncing certificate store using /etc/ssl/certs/ca-certificates.crt
Release spec: Release - built by CUBECODERS/buildbot on CCL-DEV AMP Instance Manager v1.9.5.2 built 16:29 Log output if i start with AMP LOGLEVEL=0: AMP_LOG_LEVEL=0 ampinstmgr -s Minecraft01 Webinterface error: "This task could not be completed: Starting Instance - Starting Minecraft01 (Minecraft01)." Logfile doesn't show any error or other information. I have an amp installation with four minecraft instances running as docker instances.Īfter upgrading to latest AMP version 1.9.5.2, the minecraft instances are not able to start.
0 kommentar(er)
