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

DevServices crashes immediately on Fedora #18577

Closed
Sanne opened this issue Jul 9, 2021 · 1 comment · Fixed by #18578
Closed

DevServices crashes immediately on Fedora #18577

Sanne opened this issue Jul 9, 2021 · 1 comment · Fixed by #18578
Milestone

Comments

@Sanne
Copy link
Member

Sanne commented Jul 9, 2021

Describe the bug

Any attempt to start a test on Fedora results in this exception, since #18505 :

Build failure: Build failed due to errors
	[error]: Build step io.quarkus.datasource.deployment.devservices.DevServicesDatasourceProcessor#launchDatabases threw an exception: java.lang.IllegalArgumentException: port out of range:-1
	at java.base/java.net.InetSocketAddress.checkPort(InetSocketAddress.java:143)
	at java.base/java.net.InetSocketAddress.<init>(InetSocketAddress.java:188)
	at java.base/java.net.Socket.<init>(Socket.java:232)
	at io.quarkus.deployment.IsDockerWorking.getAsBoolean(IsDockerWorking.java:43)

The problem is that I have the DOCKER_HOST variable pointing to a unix socket: unix:/run/user/1000/podman/podman.sock; this is quite common among Fedora / RHEL users.

Podman otherwise works fine, so I'd prefer if the return of this method was true - not sure what do to. Perhaps just skip this check if DOCKER_HOST starts with unix: ?

@quarkus-bot
Copy link

quarkus-bot bot commented Jul 9, 2021

/cc @stuartwdouglas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants