{"id":38281196,"url":"https://github.com/kaosagnt/boot2docker-xfs-ng","last_synced_at":"2026-03-08T05:01:56.902Z","repository":{"id":64837959,"uuid":"159247266","full_name":"kaosagnt/boot2docker-xfs-ng","owner":"kaosagnt","description":"Lightweight Linux for Toolbox2docker w/XFS filesystem","archived":false,"fork":false,"pushed_at":"2026-02-16T06:41:27.000Z","size":570,"stargazers_count":24,"open_issues_count":1,"forks_count":4,"subscribers_count":3,"default_branch":"master","last_synced_at":"2026-02-16T14:42:45.110Z","etag":null,"topics":["boot2docker","ctop","forked","iso","linux","tinycore","toolbox2docker","xfs"],"latest_commit_sha":null,"homepage":"","language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/kaosagnt.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":"MAINTAINERS","copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2018-11-26T23:35:13.000Z","updated_at":"2026-02-16T06:41:30.000Z","dependencies_parsed_at":"2023-10-16T16:27:08.764Z","dependency_job_id":"75f78b92-35ab-418e-8a1f-b78125f6c2b9","html_url":"https://github.com/kaosagnt/boot2docker-xfs-ng","commit_stats":null,"previous_names":[],"tags_count":104,"template":false,"template_full_name":null,"purl":"pkg:github/kaosagnt/boot2docker-xfs-ng","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kaosagnt%2Fboot2docker-xfs-ng","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kaosagnt%2Fboot2docker-xfs-ng/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kaosagnt%2Fboot2docker-xfs-ng/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kaosagnt%2Fboot2docker-xfs-ng/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/kaosagnt","download_url":"https://codeload.github.com/kaosagnt/boot2docker-xfs-ng/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/kaosagnt%2Fboot2docker-xfs-ng/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":30246626,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-03-08T00:58:18.660Z","status":"online","status_checked_at":"2026-03-08T02:00:06.215Z","response_time":56,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["boot2docker","ctop","forked","iso","linux","tinycore","toolbox2docker","xfs"],"created_at":"2026-01-17T01:58:56.340Z","updated_at":"2026-03-08T05:01:56.862Z","avatar_url":"https://github.com/kaosagnt.png","language":"Shell","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Boot2Docker-XFS-ng\n\nNOTE: This is a fork from the original https://github.com/boot2docker/boot2docker/\n\nIt uses TCL (TinyCore Linux 17.x) and the XFS filesystem by default.\n\nBoot2Docker is a lightweight Linux distribution made specifically to run\n[Docker](https://www.docker.com/) containers. It runs completely from RAM, is a\n~115MB download and boots quickly.\n\n## Important Note\n\nBoot2Docker is officially in **maintenance mode** -- it is recommended that users transition from Boot2Docker over to [Docker for Mac](https://www.docker.com/docker-mac) or [Docker for Windows](https://www.docker.com/docker-windows) instead.\n\nWhat this means concretely is new Docker releases, kernel updates, etc, but concerted attempts to keep new features/functionality to an absolute minimum to ensure continued maintainability for the few folks who can't yet transition to the better-suited Docker for Windows / Docker for Mac products (Windows 7 users who can't Docker for Windows at all, Windows 10 Home users who thus can't Hyper-V, VirtualBox users who thus can't Hyper-V, etc etc).\n\nSee [docker/machine#4537](https://github.com/docker/machine/issues/4537) for some useful discussion around Docker Machine also being in a similar state.\n\n## Features\n\n* Recent Linux Kernel, Docker pre-installed and ready-to-use\n* Tiny Core Linux 17.x\n* CTOP\n* XFS filesystem by default. (Will automount exisitng `ext4` filesystems).\n* VM guest additions (VirtualBox, VMware, XenServer)\n* Container persistence via disk automount on `/var/lib/docker`\n* SSH keys persistence via disk automount\n\n\u003e **Note:** Boot2Docker uses port **2376**, the [registered IANA Docker TLS\n\u003e port](http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=docker)\n\n## Caveat Emptor\n\nBoot2Docker is designed and tuned for development.\n**Using it for any kind of production workloads is highly discouraged.**\n\n## Installation\n\nInstallation should be performed via [Docker Toolbox](https://docs.docker.com/toolbox/)\nwhich installs [Docker Machine](https://docs.docker.com/machine/overview/), \nthe Boot2Docker VM, and other necessary tools.\n\n## How to use\n\nBoot2Docker is used via [Docker Machine](https://docs.docker.com/machine/overview/) \n(installed as part of Docker Toolbox) which leverages a Hyperviser Driver to\ninitialise, start, stop and delete the VM right from the command line.\n\nMachine Hyperviser drivers include:\n\n* Amazon Web Services\n* Microsoft Azure\n* Digital Ocean\n* Exoscale\n* Google Compute Engine\n*Generic\n* Microsoft Hyper-V\n* OpenStack\n* Rackspace\n* IBM Softlayer\n* Oracle VirtualBox\n* VMware vCloud Air\n* VMware Fusion\n* VMware vSphere\n\n## More information\n\nSee [Frequently asked questions](FAQ.md) for more details.\n\n#### Boot logs\n\nLogs can be found in /var/lib/boot2docker/log/\n\n#### Docker daemon options\n\nIf you need to customize the options used to start the Docker daemon, you can\ndo so by adding entries to the `/var/lib/boot2docker/profile` file on the\npersistent partition inside the Boot2Docker virtual machine. Then restart the\ndaemon.\n\nThe following example will enable core dumps inside containers, but you can\nspecify any other options you may need.\n\n```console\ndocker-machine ssh default -t sudo vi /var/lib/boot2docker/profile\n# Add something like:\n#     EXTRA_ARGS=\"--default-ulimit core=-1\"\ndocker-machine restart default\n```\n\n#### Installing secure Registry certificates\n\nAs discussed in the [Docker Engine documentation](https://docs.docker.com/engine/security/certificates/#/understanding-the-configuration)\ncertificates should be placed at `/etc/docker/certs.d/hostname/ca.crt` \nwhere `hostname` is your Registry server's hostname.\n\n```console\ndocker-machine scp certfile default:ca.crt\ndocker-machine ssh default\nsudo mv ~/ca.crt /etc/docker/certs.d/hostname/ca.crt\nexit\ndocker-machine restart\n```\n\nAlternatively the older Boot2Docker method can be used and you can add your \nRegistry server's public certificate (in `.pem` or `.crt` format) into\nthe `/var/lib/boot2docker/certs/` directory, and Boot2Docker will automatically\nload it from the persistence partition at boot.\n\nYou may need to add several certificates (as separate `.pem` or `.crt` files) to this\ndirectory, depending on the CA signing chain used for your certificate.\n\n##### Insecure Registry\n\nAs of Docker version 1.3.1, if your registry doesn't support HTTPS, you must add it as an\ninsecure registry.\n\n```console\n$ docker-machine ssh default \"echo $'EXTRA_ARGS=\\\"--insecure-registry \u003cYOUR INSECURE HOST\u003e\\\"' | sudo tee -a /var/lib/boot2docker/profile \u0026\u0026 sudo /etc/init.d/docker restart\"\n```\n\nthen you should be able to do a docker push/pull.\n\n#### Running behind a VPN (Cisco AnyConnect, etc)\n\nSo sometimes if you are behind a VPN, you'll get an `i/o timeout` error.\nThe current work around is to forward the port in the boot2docker-vm.\n\nIf you get an error like the following:\n\n```no-highlight\nSending build context to Docker daemon\n2014/11/19 13:53:33 Post https://192.168.59.103:2376/v1.15/build?rm=1\u0026t=your-tag: dial tcp 192.168.59.103:2376: i/o timeout\n```\n\nThat means you have to forward port `2376`, which can be done like so:\n\n* Open VirtualBox\n* Open Settings \u003e Network for your 'default' VM\n* Select the adapter that is 'Attached To': 'NAT' and click 'Port Forwarding'.\n* Add a new rule:\n\t- Protocol: TCP\n\t- Host IP: 127.0.0.1\n\t- Host Port: 5555\n\t- Guest Port: 2376\n* Set `DOCKER_HOST` to 'tcp://127.0.0.1:5555'\n\n#### SSH into VM\n\n```console\n$ docker-machine ssh default\n```\n\nDocker Machine auto logs in using the generated SSH key, but if you want to SSH\ninto the machine manually (or you're not using a Docker Machine managed VM), the\ncredentials are:\n\n```\nuser: docker\npass: tcuser\n```\n\n#### Persist data\n\nBoot2docker uses [Tiny Core Linux](http://tinycorelinux.net), which runs from\nRAM and so does not persist filesystem changes by default.\n\nWhen you run `docker-machine`, the tool auto-creates a disk that\nwill be automounted and used to persist your docker data in `/var/lib/docker`\nand `/var/lib/boot2docker`.  This virtual disk will be removed when you run\n`docker-machine delete default`.  It will also persist the SSH keys of the machine.\nChanges outside of these directories will be lost after powering down or\nrestarting the VM.\n\nIf you are not using the Docker Machine management tool, you can create an `ext4`\nformatted partition with the label `boot2docker-data` (`mkfs.ext4 -L\nboot2docker-data /dev/sdX5`) to your VM or host, and Boot2Docker will automount\nit on `/mnt/sdX` and then softlink `/mnt/sdX/var/lib/docker` to\n`/var/lib/docker`. The same can be done for an `xfs` partition but with the\ndisk label `bt2dckr-data` as `xfs` labels cannot be more than 12 characters.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fkaosagnt%2Fboot2docker-xfs-ng","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fkaosagnt%2Fboot2docker-xfs-ng","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fkaosagnt%2Fboot2docker-xfs-ng/lists"}