Micah Abbott
Micah Abbott
It's been a while since I've manually tried to do `ostree init` to create a new repo, so I blindly used the command as is and got an error message...
In the error situation covered by [RHBZ#1542144](https://bugzilla.redhat.com/show_bug.cgi?id=1542144), it is possible to end up with a system container that is only partially installed. In this partial-install state, the `atomic images list`...
Migrated from downstream [RHHBZ#1427606](https://bugzilla.redhat.com/show_bug.cgi?id=1427606); please see BZ for complete information. The `-n` flag appears to be ignored if the `run` label of the image does not have a `NAME` field...
Currently, the only documentation available (that I was able to find) for `atomic verify` is the inline help: ``` # atomic verify --help usage: atomic verify [-h] [--no-validate] [--storage STORAGE]...
While banging on #819, I found the following regarding ports: ``` $ sudo ./atomic trust add -t insecureAcceptAnything registry_domain:0 $ sudo ./atomic trust add -t insecureAcceptAnything registry_domain:0000 $ sudo ./atomic...
When using `atomic verify` I expected to get a clean output for individual images contained in a layered image, where each image had its own version information. For example: ```...
Currently, `atomic verify` will return 0 when the argument to the command is an image with a specific tag and there is no update image locally. ``` # docker images...
It would be a 'nice to have' if users could retest a single context with the `bot, retest this please` command
As pointed out in #238, some of our roles are doing value comparisons, but the error messages do not include the expected values. We should do an audit of the...
In the most recent RHELAH release, we got bit by a bug ([RHBZ #1454292](https://bugzilla.redhat.com/show_bug.cgi?id=1454292)) where the `sssd` container would not start when using the `atomic run` command. We should add...