[WIP] Add dockefiles for modules

[nikfot]

As part of my postgrad thesis I have created along along with @fotioudim dockerfiles for the modules as well as a process to build and deploy them for local development and learning purposes.

THe work is still in progress and will be accompanied by more changes but the current ones are:

->Add dockerfiles for the following:
  * libraries of the framework used as base docke image
  * supervisor/simulator dockerfile
  * consumer tool dockerfile for building the artifact

->Implement makefile command for running publishclock.

->Add docker compose

->Use buildkit to build for different platforms

[nikfot]

Hello,

Please if you find time take a look at what we have created. We have more to contribute in the coming time, we created this PR as a first contact.

Let us know your feedback on this.

Thanks,
Nikos

[CesarCoelho]

Hi Nikos, thank you for your contribution. We are now working on v4.0, I will try to integrate your input into the NMF.

[CesarCoelho]

Can you remove the log0.log.1 file, and change the PR to the v4.0 branch?

[nikfot]

Hello @CesarCoelho ! Happy to get news on this PR. The fact is that a lot more work has been done from me and @fotioudim on that matter that involves even further contributions can be done. I will look i to updating some stuff for this part, dut we would be delighted if we could sync further on this piece of work ( that is part of our postgrad thesis,soon to be public)

[CesarCoelho]

I see that you based your containers on the sdk-package file system structure. The file system structure on the sdk-package was the one used for OPS-SAT and it was quite strange. They were running everything as root. For Phi-Sat-2 we fixed this and properly run the Apps into dedicated linux users, so there is already some degree of basic isolation. This has been captured also on the RPi implementation here (space-file-system): https://github.com/NanoSat-MO-Framework/nmf-mission-raspberry-pi/
(maybe you have seen that repository already)

I would like to generalise the deployment used in Phi-Sat-2 and make it the default for all future NMF missions. Of course that means that the sdk-package will have to be updated/changed. So my advice is to not rely too much on it.
Note that the nmf-mission-raspberry-pi already includes a docker container for the deployment of the supervisor.

[nikfot]

I had seen the repository, but not the dockerfile. We have taken this I think a step further. We have a working PoC both for OpsSat and for RaspberryPi that can achieve a greater level of abstraction as well. If you're interested we'd be happy to contribute some of our work in either projects in small pieces each time.

Is the Phi-Sat implementation locked or you are still onboarding stuff, so if we make a contribution and it is accepted it will be onboard the PhiSat?

[CesarCoelho]

The Phi-Sat-2 mission was launched last year. At some point there was an open call for ideas to deploy new apps on Phi-Sat-2.
The NMF specific parts of the implementation for Phi-Sat-2 are not available to the public, unfortunately.
However, a big chunk of the updates were directly performed into this nmf main repo (branch: phi-sat-2). The new Version 4.0 will include all those changes.
We are certainly open to contributions!

[nikfot]

@CesarCoelho thanks for the insights. In the weekend I'll see what we can take out of our work and open PRs for it piece by piece in smaller chunks, so we can discuss if needed for some changes.

[CesarCoelho]

Alright, thank you. Please create the PRs against the v4.0 branch.

[CesarCoelho]

@nikfot Just to let you know that v4.0 has been released today. If you want to create PRs, please do it on branch v5.0