[007]: Add an nsinit demo launching a container from IPFS #22
Conversation
This is the example filesystem used for my nsinit container demo [1]. [1]: ipfs-shipyard/container-demos#22
|
@wking may be easier to turn this into |
| file permissions][no-exec], so you can't launch `nsinit` directly from | ||
| your IPNS directory. As a workaround, the demo `Makefile` currently | ||
| extracts the IPFS directory to your local filesystem, and then tweaks | ||
| the file mode locally. |
There was a problem hiding this comment.
@whyrusleeping maybe we can add perms to unixfs soon? we should consider it for sure in next week's sprint. ipfs/team-mgmt#5
|
@wking this looks great. i havent tried it yet, but maybe i can try it tomorrow. |
|
On Thu, Apr 16, 2015 at 05:59:26PM -0700, Juan Batiz-Benet wrote:
Maybe I should make it [101], since it's the first demo in a |
4c32056 to
075aaa4
Compare
Without bothering with Docker's image format, layer tarballs, etc.
Make the IPFS key less mysterious ;).
Without this running you can still 'ipfs get ...' local objects, but remote objects will give you: $ ipfs ls QmYRpzwXkSnCPPNL4b2gn5AFnyyMHFxhS9Nrbau5ycw92H Error: blockstore: block not found
075aaa4 to
94a4f54
Compare
|
After discussion yesterday, I've renumbered this to 007.
|
You can still build it from source if you want, but this lets you skip that step if you'd rather. I've also included some of the basic libraries from the Gentoo stage3 so we can handle a bit of dynamic linking in Go binaries.
This is one less step folks need to run to launch from the directory, although it does mean we have something else to update if the libcontainer folks change their default config format, or tweak the default values too far. Conflicts: 007-nsinit-container-from-ipfs-filesystem/README.md
54fc898 to
9d5b2fa
Compare
Without bothering with Docker's image format, layer tarballs, etc.
Details in the demo's README.md. I'm happy to rebase around #19
(which is currently also using the 005 number) if that PR lands first.