Skip to content

Instantly share code, notes, and snippets.

@aweiteka

aweiteka/publish-atomic-registry-documentation.sh

Last active September 25, 2016 16:31
Show Gist options
  • Save aweiteka/fa7bedcf385eea366504 to your computer and use it in GitHub Desktop.
Save aweiteka/fa7bedcf385eea366504 to your computer and use it in GitHub Desktop.
Download ZIP
Publishing Atomic Registry documentation
Raw
publish-atomic-registry-documentation.sh
#!/bin/bash
git clone https://github.com/openshift/openshift-docs.git
cd openshift-docs/
sudo docker run -it --rm -v `pwd`:/docs:z projectatomic/ascii_binder asciibinder package --site=atomic-registry
# per http://www.asciibinder.org/latest/guides/maintainer_guide.html#site-file-organization
# full HTML site lands in /path/to/openshift-docs/_package/atomic-registry
# Note: files are owned by root due to container running as root.
# Non-root user doesn't have perms to write to local dir
@jlebon
Copy link

jlebon commented Mar 22, 2016

I get the following:

docker run --rm -v /home/jenkins/workspace/atomic-site-docs-ar-update/atomic-registry:/docs:z projectatomic/ascii_binder --site=atomic-registry
Usage of loopback devices is strongly discouraged for production use. Either use `--storage-opt dm.thinpooldev` or use `--storage-opt dm.no_warn_on_loop_devices=true` to suppress this warning.
/usr/bin/container-entrypoint: line 2: exec: --: invalid option
exec: usage: exec [-cl] [-a name] [command [arguments ...]] [redirection ...]

Should the Dockerfile using ENTRYPOINT instead of CMD?

@aweiteka
Copy link
Author

Try removing the --site arg. It's optional. You'll build all of the sites but it's a minor optimization.

@aweiteka
Copy link
Author

Should the Dockerfile using ENTRYPOINT instead of CMD?

Ah, yeah, that's probably it. I went back and forth on this. ENTRYPOINT feels so prescriptive that I ended up leaving it out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment