Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Address several documented usability issues #181

Merged
merged 2 commits into from
Feb 2, 2021

Conversation

AlanCoding
Copy link
Member

I just want to clear some things out

Connect #128

Connect #127

Connect #152

if command[0] in constants.runtime_files:
msg += "\nPlease specify a different --container-runtime."
msg += "\nOption avaibility: {0}.".format(
', '.join([f'{runtime}: {bool(shutil.which(runtime))}' for runtime in constants.runtime_files])
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@chrismeyersfsu I don't want to get bogged down in grammar, current demo:

You do not have podman installed.
Please specify a different --container-runtime.
Detected installed: podman: False, docker: True.

I will change this wording, if you will tell me exactly what it should say, because it's going to be really easy to second-guess and iterate on a million tiny changes.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You do not have podman installed.
podman is the default container runtime. Please either install podman or specify an alternative supported container runtime by passing --container-runtime on the command line. Below are the list of supported container runtime's and whether or not they were found on your system.
podman not installed
docker installed

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

podman is the default container runtime.

That doesn't make sense for this error. It could have been the default, or it could have been the user-provided value by --container-runtime=podman (or repeat this situation for docker). The default and the value we're trying to use are not the same things.

I'll delete that sentence and see how it looks.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You do not have docker installed.
Please either install docker or specify an alternative container runtime by passing --container-runtime on the command line.
Below are the supported container runtimes and whether or not they were found on your system.
podman: not installed, docker: not installed

with latest commit, tested.

@AlanCoding
Copy link
Member Author


2021-01-15 16:31:01.665869 \| ubuntu-bionic \| �[0m�[91m+ rm -rf /tmp/venv
--
1612 | 2021-01-15 16:31:01.665875 \| ubuntu-bionic \| �[0mRemoving intermediate container 4a329f552424
1613 | 2021-01-15 16:31:01.665881 \| ubuntu-bionic \|  ---> 41fc09e05c43
1614 | 2021-01-15 16:31:01.665888 \| ubuntu-bionic \| Step 11/14 : FROM $ANSIBLE_RUNNER_IMAGE
1615 | 2021-01-15 16:31:01.665894 \| ubuntu-bionic \|  ---> 8c239b44e7ea
1616 | 2021-01-15 16:31:01.665900 \| ubuntu-bionic \| Step 12/14 : COPY --from=galaxy /usr/share/ansible /usr/share/ansible
1617 | 2021-01-15 16:31:01.665906 \| ubuntu-bionic \|  ---> Using cache
1618 | 2021-01-15 16:31:01.665912 \| ubuntu-bionic \|  ---> c0bf1719d623
1619 | 2021-01-15 16:31:01.665918 \| ubuntu-bionic \| Step 13/14 : COPY --from=builder /output/ /output/
1620 | 2021-01-15 16:31:01.665924 \| ubuntu-bionic \| failed to get destination image "sha256:c0bf1719d623e57f9d7f9fbd5d0f7a19bceb9e483e98bf10e43b3d13fab05038": No such image: sha256:c0bf1719d623e57f9d7f9fbd5d0f7a19bceb9e483e98bf10e43b3d13fab05038


looks like a re-occurrence of the cleanup bugs

@AlanCoding
Copy link
Member Author

recheck

@AlanCoding AlanCoding requested a review from pabelanger January 15, 2021 21:18
@AlanCoding AlanCoding marked this pull request as ready for review January 15, 2021 21:18
@AlanCoding
Copy link
Member Author

No idea what's going on here

Error: could not get runtime: cannot open /home/zuul/.config/containers/storage.conf: open /home/zuul/.config/containers/storage.conf: file exists

@AlanCoding AlanCoding closed this Feb 2, 2021
@AlanCoding AlanCoding reopened this Feb 2, 2021
@AlanCoding AlanCoding added the gate label Feb 2, 2021
@ansible-zuul ansible-zuul bot merged commit 7033a86 into ansible:devel Feb 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants