Hello, this is not a tool per se but couldn't find a better section to publish it up.
This is a very simple repository to set up an L2J server using Docker, which, most of the time, makes things easier.
If you intend to use Windows, keep in mind Docker is garbage on it so consider using Linux (it works pretty well).
You can follow up the instructions from here https://github.com/Ruk33/l2j-docker/tree/master
You will need:
1 - Docker, https://www.docker.com/get-started
2 - Docker compose, https://docs.docker.com/compose/install/
What's the difference from https://hub.docker.com/r/l2jserver/l2j-server-docker?
Services are separated and not bundled together, which in theory, it should make it easier to have the servers distributed in separated machines (although this is just theory, I may be assuming too much, please correct me if I'm wrong)
Regards.
L2J in Docker
Forum rules
READ NOW: L2j Forums Rules of Conduct
READ NOW: L2j Forums Rules of Conduct
- Zoey76
- L2j Inner Circle
- Posts: 7005
- Joined: Tue Aug 11, 2009 3:36 am
Re: L2J in Docker
Hello, as we understand different services shouldn't be bundle together, but we created a first docker implementation thinking that out community may not be familiar with Docker and this would be a good great step.
Anyway, great job!
Anyway, great job!
Powered by Eclipse 4.30
| Eclipse Temurin 21
| MariaDB 11.3.2
| L2J Server 2.6.3.0 - High Five ![๐](//cdn.jsdelivr.net/gh/twitter/twemoji@latest/assets/svg/1f680.svg)
Join our Discord! ![๐ฎ](//cdn.jsdelivr.net/gh/twitter/twemoji@latest/assets/svg/1f3ae.svg)
![๐ฌ](//cdn.jsdelivr.net/gh/twitter/twemoji@latest/assets/svg/1f4ac.svg)
- nonom
- L2j Veteran
- Posts: 649
- Joined: Wed Mar 11, 2009 10:34 pm
- Location: Magmeld
Re: L2J in Docker
Docker in Windows is starting to be more lighter and fast with WSL2. Anyways it doesn't matters since I'm using it only for building images.
About your Dockerfiles, try to unify the RUN* commands in one. You should use only WORKDIR at the end, to move between directories is more fast with cd into the RUN pipeline. Where do you load the gameserver config?
The approach is not much different than what we have except you split the docker-compose.yml.
We are coding a starter cloud version so any feedback is welcome in the future.
By other side I like what you did with the cli container; doing the same for the cloud but in a different approach (one to many).
Keep up the good work!
About your Dockerfiles, try to unify the RUN* commands in one. You should use only WORKDIR at the end, to move between directories is more fast with cd into the RUN pipeline. Where do you load the gameserver config?
The approach is not much different than what we have except you split the docker-compose.yml.
We are coding a starter cloud version so any feedback is welcome in the future.
By other side I like what you did with the cli container; doing the same for the cloud but in a different approach (one to many).
Keep up the good work!