Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does not work with prebuild jar #10

Open
Samistine opened this issue May 10, 2016 · 3 comments
Open

Does not work with prebuild jar #10

Samistine opened this issue May 10, 2016 · 3 comments

Comments

@Samistine
Copy link

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
Copy link
Owner

nimmis commented May 10, 2016

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
Copy link
Owner

nimmis commented May 10, 2016

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
Copy link

j-lorenzo commented May 9, 2017

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants