-
Notifications
You must be signed in to change notification settings - Fork 33
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
Run master branch as Docker image #9
Comments
Also, I don't care about running in Docker to be honest, I am basically just asking how to run from the |
Ok, I answered my own question 👍 I decided not to use Docker - for me it's overkill. I cloned the repo, installed go, built the binary and created a daemon for vi /lib/systemd/system/linx-server.service contents:
Start it systemctl enable linx-server.service
systemctl start linx-server.service |
instead of specifying "andreimarcu/linx-server" as the docker image you'd have to clone the rep and specify build path at the docker run command. |
Ok thanks @onvrb For anyone else who is not a docker expert, I figured out how to do this, maybe this helps somebody... This is just an example, change git clone https://github.com/ZizzyDizzyMC/linx-server
cd linx-server
docker build -t linx-master .
LD=/tmp/linx
mkdir $LD $LD/meta $LD/files
cp linx-server.conf.example $LD/linx-server.conf
docker run -p 8080:8080 -v $LD/linx-server.conf:/data/linx-server.conf -v $LD/meta:/data/meta -v $LD/files:/data/files linx-master -config /data/linx-server.conf |
I have followed your instructions, but get error with permission when uploading file. Do I need to do anything with the permission of the directories created?
|
Thanks for this project/fork!
I was able to run the docker image, but I wanted to use the
default-random-filename = false
flag. Seems that running it via...doesn't get you the latest bits that have that flag available.
I'm not good at Docker - does anyone know the right way to run it "locally" from the cloned repo? Or a way to invoke Docker so it grabs the
master
branch?🙏
The text was updated successfully, but these errors were encountered: