[Fiware-developer-experience] Issues with images and datasets

[David Muriel]

On Wed, Oct 28, 2015 at 11:17 AM, Pablo Fernández Moniz
<pablofernandezmoniz at gmail.com> wrote:
> Hello,
>
> We have being detected some problems with the images and the datasets
> provided and wanted to ask in we are doing something wrong or just notify
> about them:
>
> Issue with "bitergia/ul20-client" image
>
>  We have been experiencing a weird issue with the "bitergia/ul20-client"
> image:
>
>  Whenever we stop the fiware-devguide-app stack and start it again we
> receive an "ERROR: No thermal sensors found using acpi" message.

That image is a simple Ultralight 2.0 client to generate some testing
sensors and readings for IDAS.  By default, it uses acpi to get some
readings from the host, but you can change that option (--acpi) in
docker-compose.yml to any of the other two available, --sys to use the
/sys interface or --fake (along with --min and --max) to generate a
fake sensor with random readings.  Also, you can disable this
container altogether by commenting out its section on
docker-compose.yml, as no other container depends on this one right
now.

>  To replicate the poblem, you can follow the next steps:
>
> Start the devguide stack with docker-compose up
> Stop the containers with Ctrl+C
> Start the devguide again once all the containers are closed (docker-compose
> up)
>
>  We also provide you with a screenshot of the error message in the attached
> image named thermal-error-message.png.

I'll try to replicate the problem.

>  So far, the workaround we have been doing is simply docker rm and docker
> rmi both the container and the ul20-client image. After the deletion,
> docker-compose up leaves the stack workable again.

Just removing the container should be enough, there's no need to
remove the image.  We usually do a docker-compose rm to remove the
containers after stopping.  That way we always start with a clean set
of containers.


Regards,

-- 
David Muriel.