Code Monkey home page Code Monkey logo

dockercraft's Introduction

The Moby Project

Moby Project logo

Moby is an open-source project created by Docker to enable and accelerate software containerization.

It provides a "Lego set" of toolkit components, the framework for assembling them into custom container-based systems, and a place for all container enthusiasts and professionals to experiment and exchange ideas. Components include container build tools, a container registry, orchestration tools, a runtime and more, and these can be used as building blocks in conjunction with other tools and projects.

Principles

Moby is an open project guided by strong principles, aiming to be modular, flexible and without too strong an opinion on user experience. It is open to the community to help set its direction.

  • Modular: the project includes lots of components that have well-defined functions and APIs that work together.
  • Batteries included but swappable: Moby includes enough components to build fully featured container systems, but its modular architecture ensures that most of the components can be swapped by different implementations.
  • Usable security: Moby provides secure defaults without compromising usability.
  • Developer focused: The APIs are intended to be functional and useful to build powerful tools. They are not necessarily intended as end user tools but as components aimed at developers. Documentation and UX is aimed at developers not end users.

Audience

The Moby Project is intended for engineers, integrators and enthusiasts looking to modify, hack, fix, experiment, invent and build systems based on containers. It is not for people looking for a commercially supported system, but for people who want to work and learn with open source code.

Relationship with Docker

The components and tools in the Moby Project are initially the open source components that Docker and the community have built for the Docker Project. New projects can be added if they fit with the community goals. Docker is committed to using Moby as the upstream for the Docker Product. However, other projects are also encouraged to use Moby as an upstream, and to reuse the components in diverse ways, and all these uses will be treated in the same way. External maintainers and contributors are welcomed.

The Moby project is not intended as a location for support or feature requests for Docker products, but as a place for contributors to work on open source code, fix bugs, and make the code more useful. The releases are supported by the maintainers, community and users, on a best efforts basis only, and are not intended for customers who want enterprise or commercial support; Docker EE is the appropriate product for these use cases.


Legal

Brought to you courtesy of our legal counsel. For more context, please see the NOTICE document in this repo.

Use and transfer of Moby may be subject to certain restrictions by the United States and other governments.

It is your responsibility to ensure that your use and/or transfer does not violate applicable laws.

For more information, please see https://www.bis.doc.gov

Licensing

Moby is licensed under the Apache License, Version 2.0. See LICENSE for the full license text.

dockercraft's People

Contributors

aduermael avatar aranaea avatar dave-tucker avatar gdevillele avatar jbyoshi avatar jessfraz avatar leonhartx avatar luludotdev avatar ricdevz avatar thajeztah avatar thibaultcha avatar vieux avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

dockercraft's Issues

Dockerfile missing EXPOSE command

Should be self-explanatory. This should make the image usable via -P and also easier to understand for people who don't look at the image source code.

PR: #64

Running Docker commands from "T"

Pressing "T" currently opens the messaging window where you can run Docker commands. However it was not specified that your commands must be prepended with a / (ie /docker run ...). This should either be documented, or the messaging window should support plain old docker run ....

Thoughts?

Can I run command directly into it?

I want dockercraft can be run command directly into minecraft server from
docker exec
I want to use it with docker SDKs

Thanks,
Wiput Pootong

Add networks support with Minecraft beacons

  • add beacons on containers when they connect to a network (event triggered) WIP
  • reserve an area in the MC world to list the networks with "network shrines" (1 beacon with color + 1 sign with name, per network maybe)

Change Worldseed?

Hey there,

I would like to change the World-Seed of my Dockercraft-World, would this be possible? Im thinking about just creating a normal Minecraft World, with my Dockercraft Containers isolated in some kind of selfmade Bedrock Formation or something. Would this be possible, would it be possible to generate a new ("normal") world with the Docker Containers in a spot? Cleaning up by hand wouldnt be a problem, though. Im not that into cuberite servers, so I thought, I just ask for some support here :)
Thanks in advance.

~Jan

Enhancement - Consider supporting other game clients

Perhaps also have a go at visualizing Docker in games such as mari0 or Garrysmod.
I feel like this would be highly beneficial to the project, and would increase my productivity 500% (especially when I'm visualizing docker with portals).

Always get stop after startup complete

I got this message and the server auto-shutdown by itself:

$ docker-compose up
dockercraft_1 | Log: [10:40:52] --- Started Log ---
dockercraft_1 | Log: [10:40:52] Cuberite Jenkins clang x64 Release (master) build id: #236
dockercraft_1 | Log: [10:40:52] from commit id: da20a8a09b324c07915c8468e43c4fb208c118f9 built at: Fri  6 Nov 11:27:03 CET 2015
dockercraft_1 | Log: [10:40:52] Creating new server instance...
dockercraft_1 | Log: [10:40:52] Reading server config...
dockercraft_1 | Log: [10:40:52] Starting server...
dockercraft_1 | Info: [10:40:52] Compatible clients: 1.7.x, 1.8.x
dockercraft_1 | Info: [10:40:52] Compatible protocol versions 4, 5, 47
dockercraft_1 | Warning: [10:40:52] WebServer: The server is running in unsecured HTTP mode.
dockercraft_1 | Info: [10:40:52] Put a valid HTTPS certificate in file 'webadmin/httpscert.crt' and its corresponding private key to 'webadmin/httpskey.pem' (without any password) to enable HTTPS support
dockercraft_1 | Warning: [10:40:52] Cannot open file "crafting.txt", no crafting recipes will be available!
dockercraft_1 | Log: [10:40:52] Could not open the furnace recipes file "furnace.txt". No furnace recipes are available.
dockercraft_1 | Log: [10:40:52] Could not open the brewing recipes file "brewing.txt". No brewing recipes are available.
dockercraft_1 | Log: [10:40:52] -- Loading Plugins --
dockercraft_1 | Log: [10:40:52] Initialized ChatLog v.3
dockercraft_1 | Log: [10:40:52] Initialised Core v.15
dockercraft_1 | Log: [10:40:52] Initialised Docker v.1
dockercraft_1 | Log: [10:40:52] Initialized TransAPI v.1
dockercraft_1 | Log: [10:40:52] -- Loaded 4 Plugins --
dockercraft_1 | Warning: [10:40:52] Initialize: Cannot read monsters.ini file, monster attributes not available
dockercraft_1 | Warning: [10:40:52] Cannot open file Prefabs/Villages/PlainsVillage.cubeset for reading
dockercraft_1 | Warning: [10:40:52] Cannot open file Prefabs/Villages/SandVillage.cubeset for reading
dockercraft_1 | Log: [10:40:53] Startup complete, took 996ms!
dockercraft_1 | Log: [10:40:53] Shutting down server...
dockercraft_1 | Log: [10:40:54] Unloading worlds...
dockercraft_1 | Log: [10:40:54] Disabled Core!
dockercraft_1 | Log: [10:40:54] Disabled TransAPI!
dockercraft_1 | Log: [10:40:54] Cleaning up...
dockercraft_1 | Warning: [10:40:54] Couldn't notify the input thread; the server will hang before shutdown!
dockercraft_1 | Log: [10:40:54] Shutdown successful!
dockercraft_1 | Log: [10:40:54] --- Stopped Log ---
srv_dockercraft exited with code 0
Gracefully stopping... (press Ctrl+C again to force)

And my docker compose yml is:

dockercraft:
  container_name: srv_dockercraft
  image: gaetan/dockercraft
  volumes:
    - "/var/run/docker.sock:/var/run/docker.sock"
  ports:
    - "25565:25565"

Still progress in here?

Hey guys :)

I just wanted to ask, if you guys are still developing on this here (for sure its slow, because this is not your main work you do, understandable), but the last posts are from december last year, nothing new since then, are things still going :)?

Proposal: Docker Machine Integration

Following on from the discussion in #19, here is a mock up of what integration with Docker Machine could look like.

The player gets dropped in to a lobby when connecting:

screenshot 2015-12-06 19 01 57

On each of the portals is a sign that gives the name of the "Machine" it represents.
Stepping through the portal will teleport the player to the world where they can interact with that machine, much like the default Dockercraft world today... The only difference being that we have a portal that will take us "back" to the lobby world.

We'll support two modes of use:

  1. When you bind mount the docker socket, we will create a "default" machine and use the mounted socket to communicate with the Docker API. This is for backwards compatibility.
  2. Instead of mounting the one socket, you can mount your entire .docker folder which will create a portal for each of your machines
    Portals are added in a straight line, first to the left of the existing portals, then to the right. This means that the "default" portal will always be dead centre and that the line should extend evenly in each direction.

Under the hood, we use libmachine to query the list of created machines and to get the necessary certificates to set up a secure API connection over HTTPS.

unsupported protocol version

I've just built the docker image using the master branch,

running minecraft version 1.11.2
docker for mac version 1.13.1
OS X Sierra(10.12.3)

The docker image builds and runs with no errors.

After i do the "add server", which i point to "localhost", then i click on my new server to launch and get the error "Unsupported protocol version 316, please use one of these versions: 1.8.x, 1.9.x, 1.10.x"

Cubrite vendoring and update

per @ricardotk 's suggestion in #70 :

  • consider vendoring Cubrite (and plugins) using submodules.
  • also, update Cubrite to the latest version

Images, Volumes, Networks, Machines...

I would like to open a discussion, to see how we could display more informations in Dockercraft, also allow for more ingame interactions with the Docker engine (new levers, buttons...etc).

This is a picture of our original plan:
screen shot 2015-11-19 at 5 54 56 am

The columns with colored stripes were supposed to represent docker images available on the host, with one color per layer. On each image we could have "run" and "remove" buttons (but how would we give parameters when pushing "run"?)

By the way, I'm using Magicavoxel to prototype, it's free and pretty fun.

We should also find a way to represent networks and volumes.

It would be great to consider Docker Machine as well...

Now the big question is, how do we keep Dockercraft simple with all these features? Also, how do we support scale?

It may be unusable with several machines, networks, and hundreds of containers...
Maybe we could have dynamic zones, portals...

I guess we should try to agree on something before rushing on implementation. Let's prototype!

Proposal: Make container start/stop automatable using Redstone

We could do this as follows:

  • Populate a "Command Block" with the correct /docker command to start and/or stop a container
  • This block can be activated
    • a) With a button (placed on top of it)
    • b) With redstone

With the latter, a circuit such as this one can be used to implement something similar to Docker Compose :)

screenshot 2015-11-23 13 10 10

A big benefit in my book is that we can vary container start order by using more inverters

Why did this die?

It has a lot of use for new and experienced Docker users... is there a community fork? If not I'll make one!

Container control not working

I am attempting to test docker craft and having issues with container interaction within the client.
Once connected to the server I can see running containers, but the start/stop switch and remove button as well as /docker commands are not working.
If I start/stop a container from the command line, I can see that reflected in game

Host: CentOS7
Kernel: 3.10.0-229
Docker Ver: 1.8.2-7

Running latest dockercraft image

Video of issue
https://youtu.be/dYKTEmlsYNE

Avatar dies of hunger long before reaching end of image road.

Description of problem:
I have a lot of containers running, so many in fact that poor Steve simply can't reach the end before dieing from hunger.

docker version:
Client:
Version: 1.9.0
API version: 1.21
Go version: go1.5.1
Git commit: 76d6bc9
Built: Tue Nov 3 21:17:48 UTC 2015
OS/Arch: darwin/amd64

Server:
Version: 1.9.0
API version: 1.21
Go version: go1.4.3
Git commit: 76d6bc9
Built: Tue Nov 3 19:20:09 UTC 2015
OS/Arch: linux/amd64

docker info:
Containers: 323
Images: 504
Server Version: 1.9.0
Storage Driver: aufs
Root Dir: /mnt/sda1/var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 528
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.1.12-boot2docker
Operating System: Boot2Docker 1.9.0 (TCL 6.4); master : 16e4a2a - Tue Nov 3 19:49:22 UTC 2015
CPUs: 1
Total Memory: 1.956 GiB
Name: dev
ID: GOB3:F2ZI:DKD6:5T5Q:UBKT:6VFS:NQBG:UHTY:72BR:SMZ7:REM7:OBCJ
Debug mode (server): true
File Descriptors: 72
Goroutines: 128
System Time: 2015-11-17T22:43:50.660412425Z
EventsListeners: 0
Init SHA1:
Init Path: /usr/local/bin/docker
Docker Root Dir: /mnt/sda1/var/lib/docker
Labels:
provider=virtualbox

uname -a:
Darwin in5441.et.local 13.4.0 Darwin Kernel Version 13.4.0: Wed Mar 18 16:20:14 PDT 2015; root:xnu-2422.115.14~1/RELEASE_X86_64 x86_64

Environment details (AWS, VirtualBox, physical, etc.):
VirtualBox

How reproducible:
Just don't clean up after yourself for a month or two.

Steps to Reproduce:

  1. Don't docker rm any containers
  2. wait until you have a couple hundred
  3. walk of shame

Actual Results:
Hunger kills Steve

Expected Results:
Either hunger could be disabled, or turn docker road into docker shanty town to walk a grid instead of a single long roadway.

Additional info:
Awesome job guys! This was a lot of fun!

Failed to authenticate account

I install it to my test server, and i have a little problem

dockercraft    | [12:59:44] Startup complete, took 2393ms!
dockercraft    | [13:13:23] User root failed to auth, bad HTTP status line received
dockercraft    | [13:13:23] Kicking player root for "Failed to authenticate account!"
dockercraft    | [13:13:30] User root failed to auth, bad HTTP status line received
dockercraft    | [13:13:30] Kicking player root for "Failed to authenticate account!"
dockercraft    | [13:14:11] User root failed to auth, bad HTTP status line received
dockercraft    | [13:14:11] Kicking player root for "Failed to authenticate account!"
dockercraft    | [13:14:47] User root failed to auth, bad HTTP status line received
dockercraft    | [13:14:47] Kicking player root for "Failed to authenticate account!"

Proposal: Achievements

I think it would be interesting to add achievements in to Dockercraft, because everyone loves achievements.

We could have some that deal with features, e.g:

  • Containerstarter, start your first container
  • Destroyer of whales, destroy your first container

And some that deal with numbers of operations, e.g:

  • Containergedden, started 1000 containers

WDYT?

Proposal: K8s integration

Would be good to have the ability to integrate to running k8s cluster and just wander through pods and deployments... Maybe have some visualization of services, etc...

Connected to server but it's empty??

So I stood up Dockercraft on a Photon OS server and I am able to connect to it with no problem. However, the world is blank. I expected to see at least the container hosting the dockercraft but it is nothing but a blank world.

The only message I am getting in the portainer logs is "tcp client OnError: 111: Connection refused" over and over about 50 times a second or more.

In portainer, I setup the container with port mapping of 25575:25565, volume /var/run/docker.sock:/var/run/docker.sock and tty command -t.

Here is the results of inspecting the container.

[
{
"Id": "1d50c48284408c0158f23ae070dc8f1f1f8bf5064c947d47d427fcd3f9b49322",
"Created": "2017-12-16T23:06:27.553581001Z",
"Path": "/srv/Server/start.sh",
"Args": [],
"State": {
"Status": "running",
"Running": true,
"Paused": false,
"Restarting": false,
"OOMKilled": false,
"Dead": false,
"Pid": 8037,
"ExitCode": 0,
"Error": "",
"StartedAt": "2017-12-16T23:06:27.757120107Z",
"FinishedAt": "0001-01-01T00:00:00Z"
},
"Image": "sha256:dad8850a800d96ec7f633a8ef98ec9b39ac60b98eeb25c05079f5e63e6418d88",
"ResolvConfPath": "/var/lib/docker/containers/1d50c48284408c0158f23ae070dc8f1f1f8bf5064c947d47d427fcd3f9b49322/resolv.conf",
"HostnamePath": "/var/lib/docker/containers/1d50c48284408c0158f23ae070dc8f1f1f8bf5064c947d47d427fcd3f9b49322/hostname",
"HostsPath": "/var/lib/docker/containers/1d50c48284408c0158f23ae070dc8f1f1f8bf5064c947d47d427fcd3f9b49322/hosts",
"LogPath": "/var/lib/docker/containers/1d50c48284408c0158f23ae070dc8f1f1f8bf5064c947d47d427fcd3f9b49322/1d50c48284408c0158f23ae070dc8f1f1f8bf5064c947d47d427fcd3f9b49322-json.log",
"Name": "/mc",
"RestartCount": 0,
"Driver": "overlay2",
"MountLabel": "",
"ProcessLabel": "",
"AppArmorProfile": "",
"ExecIDs": null,
"HostConfig": {
"Binds": [
"/var/run/docker.sock:/var/run/docker.sock"
],
"ContainerIDFile": "",
"LogConfig": {
"Type": "json-file",
"Config": {}
},
"NetworkMode": "bridge",
"PortBindings": {
"25565/tcp": [
{
"HostIp": "",
"HostPort": "25575"
}
]
},
"RestartPolicy": {
"Name": "no",
"MaximumRetryCount": 0
},
"AutoRemove": false,
"VolumeDriver": "",
"VolumesFrom": null,
"CapAdd": null,
"CapDrop": null,
"Dns": null,
"DnsOptions": null,
"DnsSearch": null,
"ExtraHosts": [],
"GroupAdd": null,
"IpcMode": "",
"Cgroup": "",
"Links": null,
"OomScoreAdj": 0,
"PidMode": "",
"Privileged": false,
"PublishAllPorts": false,
"ReadonlyRootfs": false,
"SecurityOpt": null,
"UTSMode": "",
"UsernsMode": "",
"ShmSize": 67108864,
"Runtime": "runc",
"ConsoleSize": [
0,
0
],
"Isolation": "",
"CpuShares": 0,
"Memory": 0,
"NanoCpus": 0,
"CgroupParent": "",
"BlkioWeight": 0,
"BlkioWeightDevice": null,
"BlkioDeviceReadBps": null,
"BlkioDeviceWriteBps": null,
"BlkioDeviceReadIOps": null,
"BlkioDeviceWriteIOps": null,
"CpuPeriod": 0,
"CpuQuota": 0,
"CpuRealtimePeriod": 0,
"CpuRealtimeRuntime": 0,
"CpusetCpus": "",
"CpusetMems": "",
"Devices": [],
"DeviceCgroupRules": null,
"DiskQuota": 0,
"KernelMemory": 0,
"MemoryReservation": 0,
"MemorySwap": 0,
"MemorySwappiness": -1,
"OomKillDisable": false,
"PidsLimit": 0,
"Ulimits": null,
"CpuCount": 0,
"CpuPercent": 0,
"IOMaximumIOps": 0,
"IOMaximumBandwidth": 0
},
"GraphDriver": {
"Data": {
"LowerDir": "/var/lib/docker/overlay2/577ca66cce3e66d05242bded12a6b28dc73fe4e10a4714ccba21f2d853d570a8-init/diff:/var/lib/docker/overlay2/3787f6b8fabd22ffa287714fe2fb72f402720eb52b1d03e01ce64b849add7c77/diff:/var/lib/docker/overlay2/e2abe38bab171f241b0d8a22323b95cacd98100483ad54bd4b2f8a2817377080/diff:/var/lib/docker/overlay2/3a2c3a4cdf9c0e558941a1310e6aa2ef6d1d001e221da1b95118966f904d8a09/diff:/var/lib/docker/overlay2/5fdad9f1883c13f70a79b712e1845946a6e04d290450180682ef7911b58b18c5/diff:/var/lib/docker/overlay2/0c8320dc2e616060e58616df2c2316e7fdfd5634f3c12f125e89aa155d0cfe23/diff:/var/lib/docker/overlay2/17b0f491af64911cd021dd969099d0c9072a188fe992bc9c9b2480069c497562/diff:/var/lib/docker/overlay2/9622e55000efa3098b7694ad95ccc5b784fb4a02a42436aceeb9332ca9577fcb/diff",
"MergedDir": "/var/lib/docker/overlay2/577ca66cce3e66d05242bded12a6b28dc73fe4e10a4714ccba21f2d853d570a8/merged",
"UpperDir": "/var/lib/docker/overlay2/577ca66cce3e66d05242bded12a6b28dc73fe4e10a4714ccba21f2d853d570a8/diff",
"WorkDir": "/var/lib/docker/overlay2/577ca66cce3e66d05242bded12a6b28dc73fe4e10a4714ccba21f2d853d570a8/work"
},
"Name": "overlay2"
},
"Mounts": [
{
"Type": "bind",
"Source": "/var/run/docker.sock",
"Destination": "/var/run/docker.sock",
"Mode": "",
"RW": true,
"Propagation": "rprivate"
}
],
"Config": {
"Hostname": "5332b660f2a7",
"Domainname": "",
"User": "",
"AttachStdin": false,
"AttachStdout": false,
"AttachStderr": false,
"ExposedPorts": {
"25565/tcp": {}
},
"Tty": true,
"OpenStdin": false,
"StdinOnce": false,
"Env": [
"PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
"tty=true"
],
"Cmd": [],
"ArgsEscaped": true,
"Image": "gaetan/dockercraft:latest",
"Volumes": {
"/var/run/docker.sock": {}
},
"WorkingDir": "",
"Entrypoint": [
"/srv/Server/start.sh"
],
"OnBuild": null,
"Labels": {}
},
"NetworkSettings": {
"Bridge": "",
"SandboxID": "8f1cfa1f6cbe9b1b147c5d1aae9c6c67399fa2cb241452f99cbe8469b25ad58b",
"HairpinMode": false,
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"Ports": {
"25565/tcp": [
{
"HostIp": "0.0.0.0",
"HostPort": "25575"
}
]
},
"SandboxKey": "/var/run/docker/netns/8f1cfa1f6cbe",
"SecondaryIPAddresses": null,
"SecondaryIPv6Addresses": null,
"EndpointID": "7abd3911bb852325cc2ebd30cdb67526be618914e9037a36672ed44897682381",
"Gateway": "172.17.0.1",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"IPAddress": "172.17.0.5",
"IPPrefixLen": 16,
"IPv6Gateway": "",
"MacAddress": "02:42:ac:11:00:05",
"Networks": {
"bridge": {
"IPAMConfig": {},
"Links": null,
"Aliases": null,
"NetworkID": "d39e6ff4a80b67e36e6e12018bb68cd0130d97d2ae7374f8060a4947cb52351b",
"EndpointID": "7abd3911bb852325cc2ebd30cdb67526be618914e9037a36672ed44897682381",
"Gateway": "172.17.0.1",
"IPAddress": "172.17.0.5",
"IPPrefixLen": 16,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": "02:42:ac:11:00:05",
"DriverOpts": null
}
}
}
}
]

Doesn't work with Docker Beta

I'm using Docker Beta for Mac and can not make the game find the dockercraft server. The container starts normally, but when I try to add a new server, the game can not find to connect.

arm64 support

after some edits to the docker file I was able to get the dave-tucker/dockercraft to startup on my ARM64 based computer but I seem to messed something up that. all I get is an empty platform in a void everything else works just fine but I might need some help

Thank you for your time

EDIT:I am oddly still new to the docker system which is one of the reasons that I am trying to get this to work cause I thought it might add to the fun of learning.
Dockerfile.txt
.

destroyed my server

was running this on Centos 6.7 x64. Appeared to be running fine. Let my cousin play on it and worked great. Kept it running for 2 days and it took up all available blocks of memory (which was surprising but not shocking) but somehow did something that prevents all connectability so I can't even ssh into my digitalocean instance now. Getting "ssh_exchange_identification: Connection closed by remote host", so I guess I won't be running this anymore...

512Mb mem, 20G disk

Okay, now able to login, but can't do anything because "Error: database disk image is malformed"

okay, nevermind. Being able to login now I'm was able to solve it by removing the opened files used by the dead docker process.

Support Minecraft 1.9.x

When I connect using a regular Minecraft 1.9.2 client I get this in the docker logs: Client uses an unsupported protocol and the connection times out. Anyone else seeing this?

Client price?

Per the GitHub spirit, everything we raise as an issue:

The Client is just too much $$$

If I only intend to use the client to manage my docker containers, shouldn't I be able to download a "Community" version for free? Besides given its use, I now declare Minecraft should under the Devs division on par with Visual Studio so that eventually we get VSCraft.

Edit: Anyone interested donate a copy to me I'll extend/modify features you want. :)

Docker remote API: support older versions

Dockercraft currently talks only the latest version of the Docker remote API (docker 1.9), so it doesn't work when using a docker daemon older than 1.9.

from discussion in PR #14

It's too easy to remove switches and levers

I've used Dockercraft with a trackpad a few times and have left clicked instead of right clicking by accident a few times and actually removed a few buttons.

My preferred solution would be to add a handler for the HOOK_PLAYER_BREAKING_BLOCK hook, check if the block is within the container and if yes, prevent the player from breaking it.

We could also extend this to the floor blocks too as currently you can drop through the floor with a misplaced click!

Other possible solutions would be to use either the Gallery or ProtectionAreas plugins.

I tried a little PoC with ProtectionAreas, but this prevents players from interacting with switches/buttons as well as digging blocks.

One final solution would be to switch the game mode to Adventure - /gamemode 2. This allows interactions with buttons etc.. but prevents building/digging but hunger is still in effect.
I think there is a setting to stop hunger from killing Steve, so that would get around the issue... but you will still see your hunger depleting. Also, it would prevent us from allowing the player to place blocks in order to "do things" in future.

So, WDYT is the right way to proceed?

screen shot

Minecraft world empty

Hey folks,

I followed the guide, but unfortunately the minecraft world is empty :/
I am running OSX 10.11, docker-machine 0.5, docker 1.9, virtualbox.

Here are the logs of the container:

[12:33:08] --- Started Log ---
[12:33:08] Cuberite Jenkins clang x64 Release (master) build id: #236
[12:33:08] from commit id: da20a8a09b324c07915c8468e43c4fb208c118f9 built at: Fri  6 Nov 11:27:03 CET 2015
[12:33:08] Creating new server instance...
[12:33:08] Reading server config...
[12:33:08] Starting server...
[12:33:08] Compatible clients: 1.7.x, 1.8.x
[12:33:08] Compatible protocol versions 4, 5, 47
[12:33:08] WebServer: The server is running in unsecured HTTP mode.
[12:33:08] Put a valid HTTPS certificate in file 'webadmin/httpscert.crt' and its corresponding private key to 'webadmin/httpskey.pem' (without any password) to enable HTTPS support
[12:33:08] Cannot open file "crafting.txt", no crafting recipes will be available!
[12:33:08] Could not open the furnace recipes file "furnace.txt". No furnace recipes are available.
[12:33:08] Could not open the brewing recipes file "brewing.txt". No brewing recipes are available.
[12:33:08] -- Loading Plugins --
[12:33:08] Initialized ChatLog v.3
[12:33:08] Initialised Core v.15
[12:33:08] Initialised Docker v.1
[12:33:08] Initialized TransAPI v.1
[12:33:08] -- Loaded 4 Plugins --
[12:33:08] Initialize: Cannot read monsters.ini file, monster attributes not available
[12:33:08] Cannot open file Prefabs/Villages/PlainsVillage.cubeset for reading
[12:33:08] Cannot open file Prefabs/Villages/SandVillage.cubeset for reading
[12:33:09] Preparing spawn (world): 99.25% (397/400; 397.00 chunks / sec)
[12:33:09] Startup complete, took 1097ms!
[12:33:13] Player data file not found for sachsedaniel (ebca7ef266123cd18e49fb4699fd9fcd, offline ebca7ef266123cd18e49fb4699fd9fcd (unused)), will be reset to defaults.
[12:33:13] player joined
INFO[0000] Request sent http://127.0.0.1:8000/containers StatusCode: 200 
[12:33:13] executed: goproxy containers -> 0
[12:33:13] Player sachsedaniel has joined the game
[12:33:27] [sachsedaniel]: docker ps
[12:33:30] Player sachsedaniel has left the game

Best

Daniel

Mounting Docker CLI doesn't work in some cases

I did all my my test locally, with Virtual Box.
Mounting the CLI with this flag: -v /usr/local/bin/docker:/usr/local/bin/docker

But it doesn't seem to be working on Digital Ocean.
Is there a universal way to mount the CLI inside a container?

It would be better maybe to just translate all Docker commands into remote API calls.
But I don't know if there's a quick way to achieve this.

Proposal: Tutorial

So, it would be really cool if we could find a way of bringing the Docker Getting Started tutorial inside Dockercraft. Maybe we can add some cool things that are unique to us too (e.g redstone).

docker minecraft launcher

i'm finding a minecraft launcher for docker, anyone have idea? i just want Hang up all the time , i just run a docker container for ubuntu, and then instlal Minecraft.deb, is there any other way?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.