Update:
The Galaxy Docker release has been updated since this question was originally asked, and dependencies for this tool would be managed correctly in that environment now using default settings.
The later question didn’t involve a Docker image but a stand-alone Galaxy instance. The problem was due to a configuration issue that has been discussed in this Gitter chat. In short, a dependency was missing.
@lfdeoliveira First, make sure that you installed the most current Galaxy release, that you setup the installation directory correctly, and review that Gitter chat help. You are probably missing that same dependency.
For a very simple local Galaxy intended to be used by a single person, these instructions are still valid, and it it would be easiest to install tools from the ToolShed using managed dependencies, especially if you are new to server administration.
If that does not resolve the problem, and you need more help, please ask your new question in a new topic and include enough details so we can help. This would include at a minimum: the version/source of Galaxy, details about the local environment (OS, python version), and any admin configuration changes you have done so far, including tool installs and how those were done. We might need to bring in expertise from the Galaxy Admin working group, but it is fine to get that started here.