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

Why is there no image for gazebo:gzweb10? #333

Closed
jonaspetersorensen opened this issue Oct 26, 2019 · 8 comments
Closed

Why is there no image for gazebo:gzweb10? #333

jonaspetersorensen opened this issue Oct 26, 2019 · 8 comments

Comments

@jonaspetersorensen
Copy link

I can see the targets have been commented out in https://github.com/osrf/docker_images/blob/00d02282c2393ccde655fa0c333b4410a10b3985/gazebo/10/ubuntu/bionic/Makefile

# @docker build --tag=gazebo:gzweb10-bionic			gzweb10/.

Just curious to why not build it and make it available in docker hub?

@jonaspetersorensen
Copy link
Author

Doh, I see why, the build fails :P

There are at least 2 problems here:

  • The install of nodejs and related software will fail
  • (When nodejs is installed correctly) The build of gzweb will fail

@jonaspetersorensen
Copy link
Author

jonaspetersorensen commented Oct 26, 2019

I got it to build and run by changing how nodejs and related software is installed.
npm has been diststributed with nodejs for some time now, so removing the separate installation for that.
gzweb build will fail with latest nodejs versions, so I bumped back the version until I got one that worked.
Added apt-get upgrade to be able to install nodejs-legacy and curl.

Source file

Changes

# install packages
RUN apt-get update && apt-get upgrade -y && apt-get install -q -y \
    build-essential \
    cmake \
    imagemagick \
    libboost-all-dev \
    libgts-dev \
    libjansson-dev \
    libtinyxml-dev \
    mercurial \
    pkg-config \
    psmisc \
    xvfb \
    && rm -rf /var/lib/apt/lists/*

# install gazebo packages
RUN apt-get update && apt-get install -q -y \
    curl \
    && curl -sL https://deb.nodesource.com/setup_10.x | bash - \
    && apt-get install -q -y nodejs nodejs-legacy \
    libgazebo10-dev=10.1.0-1* \
    && rm -rf /var/lib/apt/lists/*

@jonaspetersorensen jonaspetersorensen changed the title Why is there no image for gzweb? Why is there no image for gazebo:gzweb10? Oct 26, 2019
@ruffsl
Copy link
Member

ruffsl commented Oct 26, 2019

Perhaps you could open a PR with your fix and ping @scpeters or @chapulina

@jonaspetersorensen
Copy link
Author

jonaspetersorensen commented Oct 26, 2019

I can try :)
Most likely there will have to be a change to the dockerfile template used to generate the gwiz dockerfile. My best guess is that it is this file?
https://github.com/osrf/docker_templates/blob/master/docker_templates/templates/docker_images/create_gzweb_image.Dockerfile.em

@ruffsl
Copy link
Member

ruffsl commented Oct 26, 2019

Yeah, having the special case for npm versioning in the template install logic might be tricky. Shame we can't just build it using the version of npm that ships with the distro list gazebo targets. Could gzweb itself be updated to use the current version, then we just modify then template to checkout a Target version of gzweb?

@jonaspetersorensen
Copy link
Author

jonaspetersorensen commented Oct 28, 2019

That would be the best option. That said, from my "late to the party/outsider" perspective I think it would require quite some work as the gzweb code is quite old, and the web world move on so very quickly.

@ruffsl
Copy link
Member

ruffsl commented Oct 29, 2019

it would require quite some work as the gzweb code is quite old, and the web world move on so very quickly.

Could you open a ticket with the gzweb repo about what you mean? I could remind some of the gazebo devs about it when seeing them at ROSCon, but I wouldn't be able to explain what would need to be improved myself.

@ruffsl
Copy link
Member

ruffsl commented Dec 23, 2019

Closing from inactivity, but PRs to fix gzweb build are welcome.

@ruffsl ruffsl closed this as completed Dec 23, 2019
moriarty added a commit to moriarty/gzweb that referenced this issue Sep 1, 2020
This should fix the current failing GitHub Workflow CI job.

Maybe Related: osrf/docker_images#334
See Also: osrf/docker_images#333

Using 7.0.0 or newer causes failures.
Bumping all dependencies also seemed to work but brings other issues.
This PR is the minimum change required.
chapulina pushed a commit to osrf/gzweb that referenced this issue Sep 2, 2020
This should fix the current failing GitHub Workflow CI job.

Maybe Related: osrf/docker_images#334
See Also: osrf/docker_images#333

Using 7.0.0 or newer causes failures.
Bumping all dependencies also seemed to work but brings other issues.
This PR is the minimum change required.
FelipeGdM pushed a commit to FelipeGdM/gzweb that referenced this issue Feb 1, 2021
This should fix the current failing GitHub Workflow CI job.

Maybe Related: osrf/docker_images#334
See Also: osrf/docker_images#333

Using 7.0.0 or newer causes failures.
Bumping all dependencies also seemed to work but brings other issues.
This PR is the minimum change required.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants