1. 1
    jstoja avatar jstoja 10 months ago | link | on: Docker's first aid for software developers

    1. You can list stopped containers with docker ps -a and then log with their name/id if you want to remember an easier version.

    2. docker system prune does both at the same time plus other useful delete, like detached networks and volumes.

    1. 1
      gsempe avatar gsempe 10 months ago | link

      For the 1st point, the container is no more listed with docker ps -a . As well, when I ask docker to print logs of the container after the launch, I get the error:
      Error response from daemon: No such container: c91a701ad8d8f
      Maybe your trick may not work systematically, don’t you think?

      For the 2nd point I was not aware of this command. I’ll try it.

      1. 1
        gsempe avatar gsempe 10 months ago | link

        By searching more on your first point, container is completely removed because I use the run command with the --rm option.
        Without this option I can get the logs after the container termination. Thank you!

        1. 1
          jstoja avatar jstoja 10 months ago | link

          Indeed :) Happy to see that it helped!

      1. 2
        gsempe avatar gsempe 10 months ago | link | on: The software engineering notebook

        After 3 years on Evernote, I switched 1 years ago to TiddlyWiki. It is free and customizable.

        Today I edit my “Tiddlers” inside Firefox and use the TiddlyFox Firefox extension to save it on my disk. Then I commit the changes in a private git repository.

        I find it handy and effective

        1. 1
          JKowalsky avatar JKowalsky 10 months ago | link

          Curious, will the move to WebExtensions cripple your usage? I just checked and it looks like the maintainers are at a loss for how to migrate given the lack of a save-to-file api. That uncertainty has prevented me from really adopting Tiddlywiki for general/desktop usage, even though it is very good on Firefox for Android.