Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(Dockerfile) #256

Merged
merged 1 commit into from
Nov 3, 2014
Merged

fix(Dockerfile) #256

merged 1 commit into from
Nov 3, 2014

Conversation

btc
Copy link
Contributor

@btc btc commented Nov 3, 2014

removed ipfs init (so that the image ships no longer ships with an identity)

TODO Maybe allow an init flag ipfs --init run? It's important to keep the initialization process simple. Open to alternatives. It would be nice to be able to ship an image that users can pull and execute in one command.

removed init so that the image ships no longer ships with an identity. 

TODO Maybe allow `ipfs --init run`?  It's important to keep the initialization process simple.
@btc btc added the status/in-progress In progress label Nov 3, 2014
@jbenet
Copy link
Member

jbenet commented Nov 3, 2014

Maybe:

# set bootstrap through ENV
ENV IPFS_BOOTSTRAP /ip4/0.0.0.0/tcp/4001

# maybe want ENTRYPOINT [1]
ENTRYPOINT ["ipfs"]

# args to IPFS
CMD ["run"]

once #251 is done

[1] From http://docs.docker.com/reference/builder/#cmd

Unlike the behavior of the CMD instruction, The ENTRYPOINT instruction adds an entry command that will not be overwritten when arguments are passed to docker run. This allows arguments to be passed to the entry point, i.e. docker run <image> -d will pass the -d argument to the entry point.

@jbenet
Copy link
Member

jbenet commented Nov 3, 2014

Maybe allow an init flag ipfs --init run?

What's the semantics if it's already inited? seems error prone. (maybe --init-once to be clear)

It's important to keep the initialization process simple.

  • 10^100

It would be nice to be able to ship an image that users can pull and execute in one command.

Completely agreed.

@btc
Copy link
Contributor Author

btc commented Nov 3, 2014

--init-once works.

Alternatively, --initialized #cheriton

@btc
Copy link
Contributor Author

btc commented Nov 3, 2014

@jbenet RTM

jbenet added a commit that referenced this pull request Nov 3, 2014
@jbenet jbenet merged commit 676ee82 into master Nov 3, 2014
@jbenet jbenet removed the status/in-progress In progress label Nov 3, 2014
@jbenet jbenet deleted the docker-init-fix branch November 3, 2014 07:34
@jbenet
Copy link
Member

jbenet commented Nov 3, 2014

@maybebtc i merged, but i still think we should change this to an entrypoint at some point.

@jbenet jbenet mentioned this pull request Nov 3, 2014
@btc
Copy link
Contributor Author

btc commented Nov 3, 2014

Ah you rewrote history 🐍

😄 I'll change over once I've had a chance to try it out.

@jbenet
Copy link
Member

jbenet commented Nov 3, 2014

@maybebtc ??? i didnt rewrite history, i just clicked Merge after seeing RTM.

@btc
Copy link
Contributor Author

btc commented Nov 3, 2014

Oh no. I didn't see your comment about ENTRYPOINT. And thought that you'd edited comment that mentioned --init run. I must've just misread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants