ign-gazebo5 Docker build fails; unable to locate package dart6-data #1004
Comments
|
Thanks for the report. I believe the problem is on these lines: Those packages are available on Bionic, you can compare against this list: But the image is building on Focal, so it should use these packages: Would you be able to give that change a try and open a pull request if it works for you? |
|
Those changes got the image to build! Thank you. I'm now tracking down a different bug that is preventing me from seeing a GUI within the Docker container. I don't think that is related to these changes to the build script, so I opened the PR for these changes. |
|
The bug that I was experiencing that prevented me from running the GUI was as follows: The The image built by My solution was to change I'm happy to provide this change in another PR (or the existing one) . However, is the Docker file still a supported use case? It's not clear to me whether the nightly build Dockerfile is intended to be a headless, isolated server or one with X forwarding capabilities. Summoning @russkel , @nkoenig , and @mjcarroll , much-appreciated original contributors to the Dockerfiles who might have guidance on their intended use. |
Ah yes, that also needs updating 😬
We've been doing a bad job at keeping that updated because we don't run any regular automated testing for it. Our Docker support is also currently split across a few different places, such as:
I'd love to have it all organized into a coherent set of Dockerfiles and build / run scripts that we can confidently point users to. We'll probably have different ones according to the use case (development of downstream projects, development of Ignition itself, CI for downstream projects, etc). @adlarkin took a look into this a while back and I believe the result was |
|
I do agree that our Docker resources/documentation is scattered across various locations, which makes it hard for us to maintain and hard for others to use. The most recent development I am aware of is https://github.com/ignition-tooling/gzdev (more specifically, https://github.com/ignition-tooling/gzdev#ign-docker-env) which is meant to provide users with an ignition environment that is GUI/GPU friendly and also supports development of ignition packages fairly easily. I think that we should consolidate all of our Docker resources into one place. Dockerhub seems to be a good place to host images, and we can either add documentation for the images on Dockerhub itself, or use Dockerhub to link to documentation elsewhere. It looks like some of this is being addressed in osrf/docker_images#378, but I'm not sure what the status is of that PR. I find https://github.com/ignition-tooling/gzdev#ign-docker-env to be very useful for day-to-day ignition development, but it requires things like https://github.com/osrf/rocker which users may or may not want to use. If we don't have an issue open already that keeps track of cleaning up our Docker resources/support, it would probably be worth opening one so that we have a way to track what Docker support/infrastructure is lacking. This would also be visible to the community so that others are aware of the current status of Docker support for ignition. |
Ah see, I didn't even list that one
+1 to that
I believe that's probably lacking input from the core Ignition team. If one of us steps up to take it to the finish line, we should wrap it up, document it, and announce it.
@adlarkin , would you be able to open one in |
👍 here's the issue I created: gazebo-tooling/release-tools#506 |
Environment
Source: Branch
ign-gazebo5, commit3c1a591ce1[Omitted rendering-related system information; problem affects Docker build]
Description
When I run the Docker build instructions from the ign-gazebo5 branch, installation fails with:
Note 1: I did not first build ign-gazebo locally from source. Am I supposed to do this first?
Note 2: I would prefer to use an official image pulled from Docker Hub, but I was not able to find one.
Steps to reproduce
ign-gazebo.Output
Console Output
The text was updated successfully, but these errors were encountered: