wsargent / docker-cheat-sheet Goto Github PK

Perhaps gVisor should be added in the security section.

Ran this command running latest docker and ubuntu - fully patched/updated:

docker network create --subnet 192.168.1.0/24 --gateway 192.168.1.1 iptastic

Wasn't expecting that

Please can someone take a look at this Travis CI errors people keep getting when trying to deploy to master. Below are some logs i got from my last attempt:

Checking white listed URLs: →

White listed:

1. [L462] 301 https://docs.vagrantup.com/v2/networking/forwarded_ports.html → https://www.vagrantup.com/docs/networking/forwarded_ports.html
   Issues :-(

Links

1. [L375] 404 https://docs.docker.com/engine/examples/running_redis_service/
2. [L489] https://engineering.salesforceiq.com/2013/11/05/a-docker-dev-environment-in-24-hours-part-2-of-2.html getaddrinfo: Name or service not known
3. [L497] 404 http://reventlov.com/advisories/using-the-docker-command-to-root-the-host
   Wrote results to ab-results-README.md.json
   Wrote filtered results to ab-results-README.md-filtered.json
   Wrote markdown table results to ab-results-README.md-markdown-table.json
   The command "awesome_bot README.md --allow-redirect --allow-dupe -w vagrantup.com" exited with 1.
   Done. Your build exited with 1.

Hi,

I'm looking for resources to migrate my compose v2 setup into docker services ... with some bash script to launch multiple docker cmd (build - push docker service).

Is documentation for Swarm in the roadmap ?
Cheers!

Could you elaborate a bit on the following comment?

Containers are not transient. docker run doesn't do what you think.

Specifically:

• define transient (is "not transient" equivalent to "persistent"?)
• what does docker run do that is not intuitive?

The link to the DOCKERFILE tutorial in https://github.com/wsargent/docker-cheat-sheet#tutorial is defective.
http://flux7.com/blogs/docker/docker-tutorial-series-part-3-automation-is-the-word-using-dockerfile/ link

Hey! Love your cheat sheet. Just wondering if you have any plans on expanding it to include Linux. Most people probably use Ubuntu or similar flavors, though I quess some would use Fedora or Arch. Ubuntu is more of what I'm looking for though.

Lemme know! :D

fyi, there is a long history of making PDF cheat sheets, and the reason is that you can print them on one page and hang them up next to your desk!

I mean the Lightbend part. Is it intended and reasonable? I did not find it in the main README.md.

Maybe you could add shipyard to your list of tools.

It would be nice if you make releases on a regular basis. A release could be done after some minor or a major edit.

Hello, we have indexd this cheat sheet to awesome-cheatsheet

Thank You !!! 🚀 🚀 🚀

I am using a grafana dokcer image. By default it runs at port 3000. How do I change it to 80

The new docker cli convention is migrating from single sub-command to pair of management commands. So, It's better to update this document to new interface.

Examples:

# docker rm my-container
docker container rm my-container

# docker ls
docker container ls

# docker run python
docker container run python

# docker pull python
docker image pull python

as multi-stage builds is a thing now (and a useful thing) it is a good idea to provide a sample example (maybe just link)

https://docs.docker.com/engine/userguide/eng-image/multistage-build/

can i translate to Indonesia?

Hey there, I'd like to use parts of this cheat sheet as a part of a larger work I'm writing. Would that be okay? Just checking since there's no license file/notice.

Thanks!

According to travis ci the following links seem to be broken:

1. [L304] 521 http://jonathan.bergknoff.com/journal/building-good-docker-images
2. [L304] 521 http://jonathan.bergknoff.com/journal/building-better-docker-images

I have this cheat sheet on my cubicle wall

Thanks for this!

I'm new to docker and appreciate the cheat-sheet. I'm probably doing something wrong, but after fighting with EXPOSE, it seems the cheat-sheet is wrong.

Exposing ports says:

If you don't want to use the -p option on the command line, you can persist port forwarding by using EXPOSE

But the documents say:

The EXPOSE instruction informs Docker that the container listens on the specified network ports at runtime. EXPOSE does not make the ports of the container accessible to the host. To do that, you must use either the -p flag to publish a range of ports or the -P flag to publish all of the exposed ports.

Hi,
Although I originally forked from your repo, I've discovered a fairly large number of inaccuracies plus decided to re-word and re-organize considerably to where there is currently only approx 20% original work and 80% modified... And as I continue to review I will make more modifications.

With that much change, it's probably not practical to submit pull requests, and I will maintain my work as a permanent fork, but you are more than welcome to update your repo from my fork as much as you might like.

Thank you much for your original work, it has been extremely useful.

putztzu
https://github.com/putztzu/docker-cheat-sheet

Hello,
I find an invalidate link in README.md line 512,
it`s like https://www.lvh.io/posts/dont-expose-the-docker-socket-not-even-to-a-container.html,
and I check out this link has changed to https://www.lvh.io/posts/dont-expose-the-docker-socket-not-even-to-a-container/

maybe it need a fix.

Hello, I wrote a tool that can validate README links (valid URLs, not duplicate). It can be run when someone submits a pull request.

It is currently being used by many projects including

• https://github.com/vinta/awesome-python
• https://github.com/enaqx/awesome-react
• https://github.com/vsouza/awesome-ios
• https://github.com/caesar0301/awesome-public-datasets
• https://github.com/veggiemonk/awesome-docker

Examples

• https://travis-ci.org/vinta/awesome-python/builds/98201707 ok ✅
• https://travis-ci.org/matteocrippa/awesome-swift/builds/96722421 link redirected / rename 🔴
• https://travis-ci.org/dkhamsing/open-source-ios-apps/builds/96763135 bad link / project deleted 🔴
• https://travis-ci.org/vsouza/awesome-ios/builds/106914621 dupe 🔴

If you are interested, connect this repo to https://travis-ci.org/ and add a .travis.yml file to the project.

See https://github.com/dkhamsing/awesome_bot for options, more information
Feel free to leave a comment 😄

make it exportable in PDF, htm with versioning and include it in the repo so you can bookmark or save it.

I don't understand the sentiment behind:

Docker image ids are sensitive information
and should not be exposed to the outside
world. Treat them like passwords.

This only seems to be the case when a public registry is being used. If you agree, will you add a note stating as much?

docker docs seem to have changed their url structure

e.g. https://docs.docker.com/reference/commandline/cli/#restart should now be https://docs.docker.com/reference/commandline/restart/