search

nimmis / docker-spigot

A docker container with spigot, builds spigot.jar on first start
175 stars 82 forks source link

Does not work with prebuild jar #10

Open Samistine opened 8 years ago

Samistine commented 8 years ago

Atempting to start a new container with spigot.jar already inside produces this in logs:

* open logfile * Run files in /etc/my_runonce/ * Running /etc/my_runonce/set_timezone... * Run files in /etc/my_runalways/ * Running /etc/my_runalways/do_build_spigot... --2016-05-10 12:23:06-- https://hub.spigotmc.org/jenkins/job/BuildTools/lastSuccessfulBuild/artifact/target/BuildTools.jar Resolving hub.spigotmc.org (hub.spigotmc.org)... * Log: Setting version to latest * Log: Building spigot version (latest) jar file, be patient failed: Name or service not known. wget: unable to resolve host address 'hub.spigotmc.org' Error: Invalid or corrupt jarfile BuildTools.jar cp: cannot stat '//minecraft/build/Spigot/Spigot-Server/target/spigot-.jar': No such file or directory ** Running /etc/my_runalways/eula... * Running /etc/rc.local... * Booting supervisor daemon... * Supervisor started as PID 44 2016-05-10 12:23:52,432 CRIT Set uid to user 0 *\ Started processes via Supervisor...... crond RUNNING pid 48, uptime 0:00:04 spigot BACKOFF Exited too quickly (process log may have details) syslog-ng RUNNING pid 47, uptime 0:00:04

nimmis commented 8 years ago

This is a docker error, this is from a previous issue "Nevermind, this is an ubuntu bug - https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1509867

After restarting docker everything worked great."

nimmis commented 8 years ago

I will add more error checking to the script to show it as a docker error and not the current not so obvious error messages.

j-lorenzo commented 7 years ago

Hi @nimmis I have the same issue with the supervisor until the last update... I build my own docker image based on the commit dc5afd963d4100f9df481e9fd504f56ac530f0c9 and it works.