Tags: gdraheim/docker-copyedit
Tags
New --podman=podman option to set an "alternative" container tool. Using the PODMAN image1 INTO image2 will use that alternative tool which defaults to podman. With FROM image1 IMPORT image2 it is possible to move an image from one container storage space to the alternative one. This should help with the mix of docker+podman we have in reality now. On the implementation side the tool does generate exitcodes greater 0 when a usage error occurs. This had been missing errornously in the past. Internally this is achieved with declaring exception types and printing them to the error-log. It will not change much in reality but some log lines may appear later. The DEVGUIDE.md now points to always run podman tests. A small bugfix for podman was integrated as well. Next up will be the integration of podman tests right into the main testsuite (instead of running the testsuite twice) which may increase the coverage as the tool has learned some tricks to get away with podman pecularities. Consider to use v1/docker-copyedit.py instead of master/docker-copyedit.py if you download directly. The tool name will change locally for v2 to docker_copyedit.py to help with testing and further integration. Also the extra "*.pyi" will be dropped soon as python2 support will be erased for v2 as well. The release 1.4 is a switch to Python3. So anyone downloading the script directly from Github may experience problems. The build system does also take advantage of type checking the code with retype+mypy. Static code analysis is simply better than just relying on a testsuite to cover everything. The docker-copyedit.py binary does support a few new options. Using "-c KEEPOUTPUTFILE=y" one can specifically keep that file instead of using -kkk. The number of -kk has also changed as the default has changed to skip the saved.tar generation. Additionally it is possible to provide a path to some --docker=/other/binary but tests with podman have shown that it is incompatible (although the bug reports show that it may be fixed in the next version of podman). The provided setup.cfg file allows to package a bdist_wheel universal distribution.
Only documentation updates here. Added DEVGUIDE.md and bumped mypy/coverage. The release 1.4 is a switch to Python3. So anyone downloading the script directly from Github may experience problems. The build system does also take advantage of type checking the code with retype+mypy. Static code analysis is simply better than just relying on a testsuite to cover everything. The docker-copyedit.py binary does support a few new options. Using "-c KEEPOUTPUTFILE=y" one can specifically keep that file instead of using -kkk. The number of -kk has also changed as the default has changed to skip the saved.tar generation. Additionally it is possible to provide a path to some --docker=/other/binary but tests with podman have shown that it is incompatible (although the bug reports show that it may be fixed in the next version of podman). The provided setup.cfg file allows to package a bdist_wheel universal distribution.
The release 1.4 is a switch to Python3. So anyone downloading the script directly from Github may experience problems. The build system does also take advantage of type checking the code with retype+mypy. Static code analysis is simply better than just relying on a testsuite to cover everything. The docker-copyedit.py binary does support a few new options. Using "-c KEEPOUTPUTFILE=y" one can specifically keep that file instead of using -kkk. The number of -kk has also changed as the default has changed to skip the saved.tar generation. Additionally it is possible to provide a path to some --docker=/other/binary but tests with podman have shown that it is incompatible (although the bug reports show that it may be fixed in the next version of podman). The provided setup.cfg file allows to package a bdist_wheel universal distribution.
The release 1.4 is a switch to Python3. So anyone downloading the script directly from Github may experience problems. The build system does also take advantage of type checking the code with retype+mypy. Static code analysis is simply better than just relying on a testsuite to cover everything. The docker-copyedit.py binary does support a few new options. Using "-c KEEPOUTPUTFILE=y" one can specifically keep that file instead of using -kkk. The number of -kk has also changed as the default has changed to skip the saved.tar generation. Additionally it is possible to provide a path to some --docker=/other/binary but tests with podman have shown that it is incompatible (although the bug reports show that it may be fixed in the next version of podman). The provided setup.cfg file allows to package a bdist_wheel universal distribution.
The release 1.4 is a switch to Python3. So anyone downloading the script directly from Github may experience problems. The build system does also take advantage of type checking the code with retype+mypy. Static code analysis is simply better than just relying on a testsuite to cover everything. The docker-copyedit.py binary does support a few new options. Using "-c KEEPOUTPUTFILE=y" one can specifically keep that file instead of using -kkk. The number of -kk has also changed as the default has changed to skip the saved.tar generation. Additionally it is possible to provide a path to some --docker=/other/binary but tests with podman have shown that it is incompatible (although the bug reports show that it may be fixed in the next version of podman). The provided setup.cfg file allows to package a bdist_wheel universal distribution.
The release 1.4 is a switch to Python3. So anyone downloading the script directly from Github may experience problems. The build system does also take advantage of type checking the code with retype+mypy. Static code analysis is simply better than just relying on a testsuite to cover everything.
The release 1.2 is based on changes to the parser. It has moved the ALL flag from the edit_image executor to the parsing routine where it will be replaced by a star `*` argument to REMOVE VOLUMES and REMOVE PORTS. With a more widespread usage a couple of small bugs did come up. This includes lowercase/uppercase handling in the parser. And the point that a missing ':version' must be put as ':latest' into the output tarball to be loaded correctly. There are more problems with people to expect to be able to use any image name where in fact the docker tagging format is quite restricted. The tool will now warn on a lot of common problems as far as they are documented in the docker documentation.
PreviousNext