Giter Club home page Giter Club logo

m3_container's Introduction

m3_container's People

Contributors

frmfl avatar gralpli avatar heppth avatar m-kress avatar maximilianschwab avatar mexx42 avatar mi-schindler avatar rudolfroedl avatar tp-doc avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

m3_container's Issues

Can't build default container

I tried to do as the manual say, and here's what I got:

PS C:\> docker pull insysicom/m3sdk_v5
Using default tag: latest
latest: Pulling from insysicom/m3sdk_v5
fdc2327896ee: Pull complete
Digest: sha256:170ac7958995539501a094c06522b159140aef78bb16bbdec00e40ac83a0acc3
Status: Downloaded newer image for insysicom/m3sdk_v5:latest
docker.io/insysicom/m3sdk_v5:latest

What's Next?
  1. Sign in to your Docker account → docker login
  2. View a summary of image vulnerabilities and recommendations → docker scout quickview insysicom/m3sdk_v5
PS C:\> docker run --rm -it -v C:\M3_Container:/workspace insysicom/m3sdk_v5 /bin/bash --login
245baec63a06 / # cd workspace
245baec63a06 /workspace # git clone https://github.com/insys-icom/M3_Container.git
Cloning into 'M3_Container'...
remote: Enumerating objects: 6431, done.
remote: Counting objects: 100% (1191/1191), done.
remote: Compressing objects: 100% (400/400), done.
remote: Total 6431 (delta 825), reused 1118 (delta 760), pack-reused 5240
Receiving objects: 100% (6431/6431), 4.47 MiB | 8.01 MiB/s, done.
Resolving deltas: 100% (4440/4440), done.
Updating files: 100% (287/287), done.
245baec63a06 /workspace # cd M3_Container
245baec63a06 /workspace/M3_Container # ./scripts/create_container_default.sh

It is necessary to build these Open Source projects in this order:
- Linux-PAM-1.5.3.sh
- zlib-1.3.sh
- lz4-1.9.4.sh
- tzdb-2023d.sh
- pcre2-10.42.sh
- openssl-3.2.0.sh
- mcip.sh
- busybox-1.36.1.sh
- mcip-tool-v4.sh
- dropbear-2022.83.sh
- metalog-20230719.sh
- dnsmasq-2.89.sh

These packages only have to be compiled once. After that you can choose to only pack the container. Choose:
    b --- build all sources and pack the container
    p --- pack the container without building the sources
    c --- cancel, do nothing

b
Building everything

Downloading packages:
--------------------------------------------
    Downloading Linux-PAM-1.5.3.sh
    Downloading zlib-1.3.sh
    Downloading lz4-1.9.4.sh
    Downloading tzdb-2023d.sh
    Downloading pcre2-10.42.sh
    Downloading openssl-3.2.0.sh
    Downloading mcip.sh
    Downloading busybox-1.36.1.sh
    Downloading mcip-tool-v4.sh
    Downloading dropbear-2022.83.sh
    Downloading metalog-20230719.sh
    Downloading dnsmasq-2.89.sh

Uninstalling packages:
--------------------------------------------
    Uninstall Linux-PAM-1.5.3.sh
    Uninstall zlib-1.3.sh
    Uninstall lz4-1.9.4.sh
    Uninstall tzdb-2023d.sh
    Uninstall pcre2-10.42.sh
    Uninstall openssl-3.2.0.sh
    Uninstall mcip.sh
    Uninstall busybox-1.36.1.sh
    Uninstall mcip-tool-v4.sh
    Uninstall dropbear-2022.83.sh
    Uninstall metalog-20230719.sh
    Uninstall dnsmasq-2.89.sh

Compiling in parallel:
--------------------------------------------
    Compile Linux-PAM-1.5.3.sh
    Compile zlib-1.3.sh
    Compile lz4-1.9.4.sh
    Compile tzdb-2023d.sh
    Compile pcre2-10.42.sh
    Compile openssl-3.2.0.sh
    Compile mcip.sh
    ----------------------------------------
    Compile busybox-1.36.1.sh
    Compile mcip-tool-v4.sh
    Compile dropbear-2022.83.sh
    Compile metalog-20230719.sh
    Compile dnsmasq-2.89.sh
    ----------------------------------------
    ----------------------------------------

Packaging the container "container_default":
--------------------------------------------
  -> Creating archive /workspace/M3_Container/working/update/rootfs.tar containing the root file system
cp: cannot stat '/workspace/M3_Container/rootfs_staging/bin/busybox': No such file or directory
failed to copy /bin/busybox

create_container_default.sh failed to build (due to conflicting install location for several packages)

Followed installation steps as mentioned here using docker image.
https://hub.docker.com/r/insysicom/m3sdk_v5

./scripts/create_container_default.sh

Install: cannot create directory '/workspace/M3_Container/working/1z4-1.9.4/install': Not a directory install: cannot create directory '/workspace/M3_Container/working/1z4-1.9.4/install': Not a directory

make[1]: * [Makefile:182: install] Error 1 make[1]: Leaving directory '/workspace/M3_Container/working/1z4-1.9.4/lib


failed due to several individual build failure. While going through the logs, it seems to be due to the PKG_INSTALL_DIR path. The source already contains an INSTALL file and the script tried to create install directory. Since linux do not allow having a directory and file sharing same this is failing. Following build scripts failed due to this

  1. pcre2-10.42.sh
  2. metalog-20220214.sh
  3. lz4-1.9.4.sh

There may be other scripts with same issue.

Fix suggestion:

change PKG_INSTALL_DIR="${PKG_BUILD_DIR}/install" to PKG_INSTALL_DIR="${PKG_BUILD_DIR}/installd"

dns lookup in sdk lxc container doesn't work out of the box

Problem: in /etc/resolv.conf there's a nameserver configured that's in a private network (192.168.200.2 in 192.168.0.0/16) so this isn't necessarily reachable from any network

Suggestion: use a public nameserver like 1.1.1.1 or 8.8.8.8 or mention that dns has to be configured

Steps to reproduce: I'm trying to build a container for an SCR Series Device (I'm not an employee of insys, so am not in the same network :) ). I followed the tutorial on how to run the sdk lxc container and proceded to https://github.com/insys-icom/M3_Container/blob/master/doc/1st_steps.md , but step 2 - cloning the git repository already fails. I worked around that by cloning it from my host and bind mounting it into the container, but the build scripts also download tarballs from the internet which won't work either. That's when I discovered that the nameserver isn't reachable.

scritps/mk_container.sh: realpath says no such file or directory

just tried copying a binary to rootfs_staging to build my own container. Unfortunately though, the script mk_container.sh failed to run at first:
$ scripts/mk_container.sh realpath: scripts/..: No such file or directory scripts/mk_container.sh: line 5: /scripts/common_settings.sh: No such file or directory
I've noticed that this is caused by realpath, which appears to have issues with the double dots at the end of its argument: scripts/..
As a workaround, I just edited the script hardcoding the $TOPDIR variable

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.