Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Podman not supported
See original GitHub issueDescription
Info
- d-m-p version : 0.28.0
- Maven version (
mvn -v) :
Apache Maven 3.6.2 (40f52333136460af0dc0d7232c0dc0bcf0d9e117; 2019-08-27T17:06:16+02:00)
Maven home: /home/kb1000/.m2/wrapper/dists/apache-maven-3.6.2-bin/795eh28tki48bv3l67maojf0ra/apache-maven-3.6.2
Java version: 1.8.0_242, vendor: Oracle Corporation, runtime: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.242.b08-0.fc31.x86_64/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "linux", version: "5.5.6-201.fc31.x86_64", arch: "amd64", family: "unix"
- Docker version : none, emulated using podman 1.8.0 from Fedora 31
- If it’s a bug, how to reproduce : Install podman on Fedora 31 using
sudo dnf install podman-dockerand try to use this Maven plugin - If it’s a feature request, what is your use case :
- Sample project : https://github.com/quarkusio/quarkus-quickstarts (tested with hibernate-search-elasticsearch-quickstart project there)
[ERROR] Failed to execute goal io.fabric8:docker-maven-plugin:0.28.0:stop (docker-start) on project hibernate-search-elasticsearch-quickstart: Execution docker-start of goal io.fabric8:docker-maven-plugin:0.28.0:stop failed: No <dockerHost> given, no DOCKER_HOST environment variable, no read/writable '/var/run/docker.sock' or '//./pipe/docker_engine' and no external provider like Docker machine configured -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
[kb1000@local-host hibernate-search-elasticsearch-quickstart]$ docker
Emulate Docker CLI using podman. Create /etc/containers/nodocker to quiet msg.
Error: missing command 'podman COMMAND'
Try 'podman --help' for more information.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:9
- Comments:21
Top Results From Across the Web
podman/troubleshooting.md at main · containers ... - GitHub
Podman: A tool for managing OCI containers and pods. ... Go language does not support sparse files correctly, which can lead to some...
Read more >MacOS. Podman. Provide fixes/workarounds for not working ...
So, we have now VM with Fedora (which has podman installed) in VirtualBox on MacOS. go to this vm (run command vagrant ssh...
Read more >Podman Installation Instructions
Podman on Mac and Windows also listens for Docker API clients, supporting direct usage of ... Note that Podman does not officially support...
Read more >Podman bind mount not working with absolute path
Issue 8302 does specify Volumes over remote are not supported. The podman remote client will try to bind mount the file on the...
Read more >1763007 – --log-opt for podman run does not work as expected
Podman supports a (limited) set of log drivers, but does not presently support setting options for these drivers.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Updating here since people seem to have bookmarked this place:
Podman evolved a bit, the better command is now:
Podman 2.0 which is in release candidate stage now supports the REST API of the docker daemon.