I keep getting the following error when I run sudo podman run command -
sudo podman run --name mysql-custom \ > -e MYSQL_USER=redhat -e MYSQL_PASSWORD=r3dh4t \ > -d rhmap47/mysql:5.5
unable to pull : error getting registries to try: invalid reference format
Hi Suhaib
Yes, this is an issue with the rendering we already saw in the past.
The issue is that:
- There should be a carry return after the `\` sign. This sign indicates the command is not yet complete and continues in the next line.
- The `>` sign should be rendered as a "continuation prompt", indicating this is not something you should write, but something the terminal is showing.
So, as Alexandre said, please try the command without the `\>` signs.
BTW, what course and version are you finding this? We should have fixed the issue, but maybe we missed a case.
Kind Regards
Jordi Sola
Hi
Are you really type the command this way:
sudo podman run --name mysql-custom \ > -e MYSQL_USER=redhat -e MYSQL_PASSWORD=r3dh4t \ > -d rhmap47/mysql:5.5
Try
sudo podman run --name mysql-custom -e MYSQL_USER=redhat -e MYSQL_PASSWORD=r3dh4t -d rhmap47/mysql:5.5
Hi Suhaib
Yes, this is an issue with the rendering we already saw in the past.
The issue is that:
- There should be a carry return after the `\` sign. This sign indicates the command is not yet complete and continues in the next line.
- The `>` sign should be rendered as a "continuation prompt", indicating this is not something you should write, but something the terminal is showing.
So, as Alexandre said, please try the command without the `\>` signs.
BTW, what course and version are you finding this? We should have fixed the issue, but maybe we missed a case.
Kind Regards
Jordi Sola
Thanks for your kind help. BTW the course version 4.2, that I'm working on is DO180.
I'm pretty sure this is in DO180, and I only found one instance of this string (looking at the PDF file.
The actual render is correct, but Jordi is correct: The backslash char (\) means "type \ and press Enter" and the shell provides the > symbol, indicating that the command is still open.
The render is correct in the current build (see attached) so I *expect* yours should display the same way. If not, please let us know.
Thanks very much.
David
Red Hat
Learning Community
A collaborative learning environment, enabling open source skill development.