ipfs-shipyard / container-demos Goto Github PK

I think our big selling point for containers right now is the ability to have a distributed registry. I think that putting more time into documentation about how to set them up will be good, a detailed readme on how to set it up, what commands to run, things that might break, etc.

Also, I think we should look at sharing and combining ipns registries. How can I pull a docker image from your registry to mine just using the ipfs tool?

I think that if we can make it trvial to use ipfs to ship docker images, we are going to be in a really good place.

Readme's in the examples need to be updated with links to ipfs/go-ipfs rather than the old jbenet/go-ipfs. 001 looked good, but I saw it in 002, 003, and 004.

1. Start astralboot
2. Boot the vm.

Discussion

1. Note: this is more of an interest for people who don't use docker machine.

1. ipfs get the vm.

Discussion

Building block for #6

Boot a VMWare .vmx machine with vmrun

ipfs daemon
ipfs mount
vmrun start Qm.... 

@phoniks commented on Tue Dec 04 2018

Seeking feedback. I'm working on enabling the user to try out the Javascript implementation of IPFS by toggling a switch on the settings page. This PR simply ads a checkbox on the DesktopSettings page. I'm particularly interested in knowing whether having this as a checkbox makes sense. Originally I had in mind, based on the original discussions of this feature, to make this setting a select component, but during coding it became obvious that doing so would add a lot of code for not very much change in user experience. Perhaps in the future, if there are other implementations that can be chosen, it may make sense to do the dropdown, but for now it doesn't seem prudent. But, perhaps since it potentially takes your node offline there should be an intermediate step between flipping the switch and actually shutting down the node and re-spawning. Maybe a quick confirmation alert?

Overview

1. Make a container.
2. Tag it.
3. Start a container elsewhere.

Discussion

1. Where is the tag stored? Is it tagged locally or is it published elsewhere?
2. Or do we have a IPFS hash entry somewhere mapping tags to addresses of images?
3. Future: what about sharing and propagating said tags?

1. make a container.
2. start the containers with swarm or fleet
3. (they share download with each other!)

Discussion

1. Would need to look at swarm or fleet and see if modifications need to be done. If the base docker client can download from ipfs, this might not be needed. Not sure if swarm and fleet shells out or does a library call.

1. Start a container.
2. Write to it.
3. Shut it down.
4. Elsewhere, start the container.
5. boom changes.

Discussion

1. Does this require changes in unionfs?
2. Or are we talking about having ipfs as a possible layer inside a stack of unionfs?

@zignig booted a machine from bare metal with astralboot! 👍

<zignig> jbenet: I got that metal machine plugged in and astral boots metal as well.
<zignig> whyrusleeping: it uses an iPXE shim , http://ipxe.org , so it presents a menu.

would be awesome to demo this too.

@phoniks commented on Tue Dec 04 2018

Seeking feedback. I'm working on enabling the user to try out the Javascript implementation of IPFS by toggling a switch on the settings page. This PR simply ads a checkbox on the DesktopSettings page. I'm particularly interested in knowing whether having this as a checkbox makes sense. Originally I had in mind, based on the original discussions of this feature, to make this setting a select component, but during coding it became obvious that doing so would add a lot of code for not very much change in user experience. Perhaps in the future, if there are other implementations that can be chosen, it may make sense to do the dropdown, but for now it doesn't seem prudent. But, perhaps since it potentially takes your node offline there should be an intermediate step between flipping the switch and actually shutting down the node and re-spawning. Maybe a quick confirmation alert?

Maybe more don't work? Someone needs to run through and test them. Plus a lot of urls point to the old repo locations.

1. Mount ipfs
2. boot from mount

Discussion

1. This is probably more interesting as a demo if we were to find more obscure OSs to run. For example: Haiku (BeOS clone), Plan 9, one of the various Lisp machines.
2. Another interesting application for this is educational distros.

Now we have an org to incubate projects that not part of the core implementation of the protocol or discussion of the spec. That org is ipfs-shipyard created from ipfs/team-mgmt#448

Short description:

IPFS Shipyard is a venue for the community to pursue and collaborate on research experiments, products, code libraries and more around the IPFS project. It is where innovation in userland happens and where we discover and form new primitives to push to the core of IPFS.

Sounds good?

1. ipfs-add new assets
2. notify production server(s) of new assets
3. Web container automatically pins new assets and makes them available

Discussion

1. How to notify the production server? Fleet? IPFS DHT? Custom http app that listens for commands to refresh?

1. Make a data container with IPFS, load up data.
2. Start container elsewhere.
3. Boom, access to data!

Overview

This is the most useful for open data. Examples:

1. http://www.fastonline.org/CD3WD_40/CD3WD/INDEX.HTM CD3WD. This is a CD-ROM containing 900+ publications for basic infrastructure technology designed to be distributed for 3rd world countries. This library could be reformatted to work with a web. We can add an nginx server or something similar: startup this container via IPFS, and you now have access to this library.
2. https://www.govtrack.us/developers/data GovTrack publishes raw data from US Congress, specifically related to legislations that are being created or debated. Because of the size of the data, GovTrack has only a single firehose to PopVox. Can take a snapshot of this and make this available, or better yet, have GovTrack publish this data. [This might be too big to function as a good demo for this]
3. http://www.nyc.gov/html/doitt/html/open/data.shtml New York City open data
4. https://www.kickstarter.com/projects/publicresource/public-safety-codes-of-the-world-stand-up-for-safe US Public Safety codes. These are publications painstakingly created and put out into the public. He has other data here: https://public.resource.org/
5. Zipcode geolocation dataset
6. International Timezone dataset
7. OpenStreetMap dataset?

1. Locally push new code and assets
2. figure notifies production application servers
3. Production application servers uses ipfs to get new releases and pins them

Discussion

There is not as much to see with this, since the command line tooling will look the same.

Overview

1. Make a container
2. Start the container elsewhere.
3. boom it works. lazily.

Where did the publish step go? We didn't need it. :)

Discussion

1. Minimalist is referencing this with a hash
2. ipns ?

Source: https://gist.github.com/jbenet/cfd72a6caea4299f7d1a

I want to be able to say:

$ docker run -i -t /ipfs/QmBlah

and get a shell in some special environment.