GithubHelp home page GithubHelp logo

core18's People

Contributors

albertodonato avatar alfonsosanchezbeato avatar anonymouse64 avatar bboozzoo avatar cjwatson avatar flotter avatar jhenstridge avatar meulengracht avatar mvo5 avatar seb128 avatar sil2100 avatar sparkiegeek avatar valentindavid avatar vorlonofportland avatar willnilges avatar xnox avatar zyga avatar

Stargazers

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

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

core18's Issues

Sensible version number

The current version number of the core18 snap is "0.1" which is ok for the edge channel but not once we move towards beta/candidate/stable.

This is a bit of an RFC how how to pick the right version: 18.04-$seq ? where the sequence always increases? E.g. 18.04-232 and once we release a po int release we move to 18.04.1-$seq? Or should it be date based? 18.04-20180919 to indicate when the last build happend?

The opinion of @niemeyer here would be especially valuable.

Multiarch isn't working

I'm trying to build a snap for a 32 bit binary on a 64 bit dev machine. As of f87a234 it should be possible to install 32 bit libraries such as libstdc++6:i386, however, i386 doesn't seem to be enabled. If I add a :i386 packages to stage-packages in my snapcraft.yaml, the build step fails and apt recommends that I run dpkg --add-architecture i386.

I'm using the current stable core18 snap: 20190409 2019-04-12 (941)

Here is a minimal snapcraft.yaml that will reproduce it:

name: test
version: 0.0.1
summary: test
description: |
  test
grade: devel
confinement: devmode
base: core18
architectures:
  - build-on: amd64
    run-on: [i386, amd64]
parts:
  test-i386:
    plugin: nil
    stage-packages:
      - libstdc++6:i386

core18 first login experience: out-of-the-blue reboot

Is this out-of-the-blue reboot expected?

andreas@nsnx:~/Downloads$ ssh ahasenack@localhost -p 8022
The authenticity of host '[localhost]:8022 ([127.0.0.1]:8022)' can't be established.
ECDSA key fingerprint is SHA256:2yPsCwbuTqJKkJyvpbr9l0eoykpC6gD8JiIccW6UMs0.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '[localhost]:8022' (ECDSA) to the list of known hosts.
Welcome to Ubuntu Core 18 (GNU/Linux 4.15.0-112-generic x86_64)

The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.

 * Ubuntu Core:     https://www.ubuntu.com/core
 * Community:       https://forum.snapcraft.io
 * Snaps:           https://snapcraft.io

This Ubuntu Core 18 machine is a tiny, transactional edition of Ubuntu,
designed for appliances, firmware and fixed-function VMs.

If all the software you care about is available as snaps, you are in
the right place. If not, you will be more comfortable with classic
deb-based Ubuntu Server or Desktop, where you can mix snaps with
traditional debs. It's a brave new world here in Ubuntu Core!

Please see 'snap --help' for app installation and updates.
ahasenack@localhost:~$ snap list

Broadcast message from root@localhost (Tue 2020-09-22 12:59:44 UTC):

reboot scheduled to update the system
The system is going down for reboot NOW!

Connection to localhost closed by remote host.
Connection to localhost closed.

Incidentally, there was a long wait after snap list and before the broadcast appeared, I'd say close to a minute.

iptables not present in core18

The iptables binary is not included in core18, so even a snap with the firewall-control plug connected can't access it

License?

I can't seem to find the license for core18?

update-motd is installed but cannot operate on read-only /

The login experience to uc18 device is not great:

localhost login: zyga
Password: 
Last login: Wed Jan 30 14:08:45 UTC 2019 on ttyMSM0
/etc/update-motd.d/50-motd-news: 59: /etc/update-motd.d/50-motd-news: cannot create /var/cache/motd-news: Read-only file system
run-parts: /etc/update-motd.d/50-motd-news exited with return code 2
 * Ubuntu Core:     https://www.ubuntu.com/core
 * Community:       https://forum.snapcraft.io
 * Snaps:           https://snapcraft.io

This Ubuntu Core 18 machine is a tiny, transactional edition of Ubuntu,
designed for appliances, firmware and fixed-function VMs.

If all the software you care about is available as snaps, you are in
the right place. If not, you will be more comfortable with classic
deb-based Ubuntu Server or Desktop, where you can mix snaps with
traditional debs. It's a brave new world here in Ubuntu Core!

Please see 'snap --help' for app installation and updates.
zyga@localhost:~$ 

As we can see the update-message-of-the-day mechanism is active but incompatible with read only filesystem used by ubuntu core.

/etc/update-motd.d/50-motd-news: 59: /etc/update-motd.d/50-motd-news: cannot create /var/cache/motd-news: Read-only file system

Stuck with blank screen on snap-core 18 Raspi 3 B+ install

I can not login to the system anymore. This happened probably after a update without any interaction on the machine.

After power off and on again I can see the Ubuntu-Core logo for some time and afterwards a blinking cursor without any further information.
This machine did run and update for about an year without any issue.

Looking at the files on the SD card I can see this changed snap versions which are in the questionable time:
pi-kernel 58
core18 snap 1226

My Raspberry pi is a model 3 b+ with an Ubuntu-core 18.

I am a bit lost where to begin to analyse this now. Can someone please guide me to analyze/resolve this issue?

Ubuntu 18.10

On Ubuntu 18.10 this now throws an error, so I guess a new core is needed:

The linker version '2.27' used by the base 'core18' is incompatible with files in this snap:
    /home/kravietz/wps2/dist/webcookies/prime/usr/bin/python3.6 (2.28)
    /home/kravietz/wps2/dist/webcookies/prime/usr/bin/python3.6m (2.28)
    /home/kravietz/wps2/dist/webcookies/prime/usr/lib/python3.6/lib-dynload/ossaudiodev.cpython-36m-x86_64-linux-gnu.so (2.28)
    /home/kravietz/wps2/dist/webcookies/prime/usr/lib/x86_64-linux-gnu/libpython3.6m.so.1.0 (2.28)
    /home/kravietz/wps2/dist/webcookies/prime/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.4 (2.28)

Can you advise how to build and use one?

Having issues installing core18

OS: Debian GNU/Linux 9.9 (stretch) x86_64
Kernal: 4.9.0-9-amd64


Hi.

I'm trying to install League of Legends via snap but get this error message:

$ sudo snap install leagueoflegends --edge
error: cannot perform the following tasks:
- Mount snap "leagueoflegends" (35) (cannot find required base "core18")

I cloned the core18 git, but can't quite figure out how to install it.

I tried installing core18 via snap with this command:
$ sudo snap install core18

But I get this error message:
error: cannot install "core18": invalid snap type: "base"

I then tried to install snapcraft, but was unable to add the repository:
W: The repository 'http://ppa.launchpad.net/snappy-dev/tools/ubuntu eoan InRelease' is not signed.


Are there any easy way to install core18 ?

systemd can't unmount disk

I am running this default systemd mount script https://paste.gnome.org/pfdd01u96 and when I stop or disable the script the disk is unmounted but commands like fsck or resize2fs can't use it as it is still in use by something. Regular mount and umount commands work fine and the dis is not in use. The systemd script is fine so there is somekind of a problem with ubuntu core 18? How can I check what is using the disk anyway? The mount command says it is unmounted.

i386 support missing on core18-amd64

as per discussion on forum.snapcraft.io

I was recently testing my wine snaps with core18 as base and during testing I begin to notice the issue that i386 was completely broken on amd64 snap.

Are there any plans for i386 support be included on core18 amd64?

Removal of expired Let's Encrypt certificate

I hope this is the right place to raise this.
There is a Let's Encrypt certificate which expired on 30th September 2021. It is included in this snap.
Many web sites that have this certificate validating them are not working. One easy fix is to remove the "DST_Root_CA_X3.crt" certificate from the server and comment out its reference in /etc/ca-certificates.conf
However, when it is included in the core18 snap (and core20 actually) this is not so straightforward - one cannot delete files from the snap.
I think this snap should have that certificate removed.

(I tried to use unsquashfs to expand core18, remove reference to the certificate and rebuild the snap, but it ended up flagged as 'broken' so I am out of my depth trying to do that for myself.)

missing /etc/cloud/cloud.cfg.d/99-snappy-azure.cfg

The core snap has this file but I don't know why it has it or if it's necessary, the git log for the core snap seems to imply that it came from the ubuntu-core-config debian pkg, but the earliest reference to this file I could find is: snapcore/core-build@aac9e1c which implies that this file even predates that...

Is this file necessary anymore in the core18 / core20 snaps? It seems no since nobody has complained about it, but still just curious about this discrepancy.

[Suggestion] Make the motd writable

The default motd message only really needs to be read once, and it mounted a read-only, meaning users can't change it.
If it was a symlink to /etc/writable/motd then users would be able to change /etc/writable/motd to change the motd.

Beef up build instructions

The build instructions, to put it bluntly, aren't super helpful. Might I suggest we get together some more complete documentation on how one should go about building this snap on various platforms? Sure, x86 is easy, but getting this to snap to craft on a Raspberry Pi took hours of internet archaeology.

See issue #161 .

bash completion not installed if "core" snap is not installed

in a fresh Bionic container with

snap    2.34.2+18.04
snapd   2.34.2+18.04
series  16
ubuntu  18.04
kernel  4.15.0-36-generic

installing a core18 based snap:

root@b:~# snap install --edge --classic sshoot
sshoot (edge) 1.4.1 from 'ack' installed
root@b:~# snap list
Name    Version  Rev  Tracking  Publisher  Notes
core18  18       442  stable    canonical  base
sshoot  1.4.1    78   edge      ack        classic
root@b:~# readlink /usr/share/bash-completion/completions/sshoot

the bash-completion file is not installed. Installing the core snap first makes it appear:

root@b:~# snap remove sshoot
sshoot removed
root@b:~# snap install core
2018-11-09T01:48:01Z INFO Waiting for restart...
core 16-2.35.5 from 'canonical' installed
root@b:~# snap install --edge --classic sshoot
sshoot (edge) 1.4.1 from Alberto Donato (ack) installed
root@b:~# readlink /usr/share/bash-completion/completions/sshoot
/snap/core/current/usr/lib/snapd/complete.sh

fw_printenv is not present in core18

A dragon board with Ubuntu Core 18 (that is core18 as bootable base, snapd as a snap) doesn't provide the fw_printenv binary. The binary is present in the core snap but not in the core18 snap.

zyga@localhost:~$ find / -name fw_printenv 2>/dev/null 
/snap/core/x1/usr/bin/fw_printenv
/snap/core/6261/usr/bin/fw_printenv
/writable/system-data/snap/core/x1/usr/bin/fw_printenv
/writable/system-data/snap/core/6261/usr/bin/fw_printenv
zyga@localhost:~$ snap list
Name                Version       Rev   Tracking  Publisher   Notes
core                16-2.37       6261  stable    canonical✓  core
core18              18            638   beta      canonical✓  base
dragonboard         18-1          44    18/beta   canonical✓  gadget
dragonboard-kernel  4.15.0-44.47  78    18/beta   canonical✓  kernel
snapd               2.37.1        2250  beta      canonical✓  snapd
test-snapd-rsync    3.1.3         9     stable    cachio      devmode

The binary is clearly used in snapd test suite. The particular test I ran was ubuntu-core-16-arm-64:tests/main/failover:rclocalcrash but it is not specific to that test.

Tail log from failed test:

-----
+ rm -f failing.snap failBoot currentBoot prevBoot
+ rm -rf /home/tmp
+ . /home/gopath/src/github.com/snapcore/snapd/tests/lib/boot.sh
++ GRUB_EDITENV=grub-editenv
++ case "$SPREAD_SYSTEM" in
+ bootenv_unset snap_try_core
+ local var=snap_try_core
+ command -v grub-editenv
+ fw_setenv snap_try_core
/home/gopath/src/github.com/snapcore/snapd/tests/lib/boot.sh: line 33: fw_setenv: command not found

timedatectl reports wrong status for timesyncd in core18

when calling timedatectl in Ubuntu Core 18 the tool reports the status of the
systemd-timesyncd.service ...

sadly it does report it wrongly (the tool reports it inactive while the service is actually running):

ogra@pi4:~$ timedatectl
                      Local time: Wed 2020-07-01 10:52:48 UTC
                  Universal time: Wed 2020-07-01 10:52:48 UTC
                        RTC time: n/a
                       Time zone: n/a (UTC, +0000)
       System clock synchronized: yes
systemd-timesyncd.service active: no
                 RTC in local TZ: no
ogra@pi4:~$ systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled)
   Active: active (running) since Tue 2020-06-30 18:06:18 UTC; 16h ago
     Docs: man:systemd-timesyncd.service(8)
 Main PID: 779 (systemd-timesyn)
   Status: "Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com)."
    Tasks: 2 (limit: 4915)
   CGroup: /system.slice/systemd-timesyncd.service
           └─779 /lib/systemd/systemd-timesyncd

[Regression] all documentation links and explanatory text vanished from MOTD

With a recent core18 upgrade all explanatory text and the various documentation links that are shown in the MOTD messages on login have vanished on all my UbuntuCore18 installs:

it looks like this now:

$ ssh 192.168.2.85
Welcome to Ubuntu Core 18 (GNU/Linux 5.3.0-1033-raspi2 armv7l)
Last login: Fri Sep 18 12:25:11 2020 from 192.168.2.48
ogra@localhost:~$

While it is supposed to give some hints and intro text about the snap ecosystem as well as help and support URLs like:

Welcome to Ubuntu Core 18 (GNU/Linux 5.3.0-1027-raspi2 armv7l)
 * Ubuntu Core:     https://www.ubuntu.com/core
 * Community:       https://forum.snapcraft.io
 * Snaps:           https://snapcraft.io

This Ubuntu Core 18 machine is a tiny, transactional edition of Ubuntu,
designed for appliances, firmware and fixed-function VMs.

If all the software you care about is available as snaps, you are in
the right place. If not, you will be more comfortable with classic
deb-based Ubuntu Server or Desktop, where you can mix snaps with
traditional debs. It's a brave new world here in Ubuntu Core!

Please see 'snap --help' for app installation and updates.
Last login: Mon Jun 29 12:04:15 2020 from 192.168.2.48

Crash qt gui aplication (build with core 18 on ubuntu 18.04(LXD))

I build the qt application in the lxd container (image ubuntu 18.04).
I'm using ubuntu 18 04, because my applications have a dependency on qt 5.9
but after startup, my application has an error:

QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/run/user/1000/snap.hanoi-tower', please create it with 0700 permissions.
Qt: Session management error: None of the authentication protocols specified are supported
QApplication: invalid style override passed, ignoring it.
dbus[28516]: The last reference on a connection was dropped without closing the connection. This is a bug in an application. See dbus_connection_unref() documentation for details.
Most likely, the application was supposed to call dbus_connection_close(), since this is a private connection.
  D-Bus not built with -rdynamic so unable to print a backtrace
 

my snapcraft file

name: hanoi-tower
version: '1.4.testBuild8' 
summary: Hanoi Towers Game
description: |
  The Hanoi Tower is one of the most popular puzzles of the 19th century. Three bars are given, on one of which eight rings are strung, the rings differ in size and lie smaller on larger ones. The problem is to transfer the pyramid from eight rings for the least number of moves to another rod. At a time, only one ring is allowed to carry, and you can not put a larger ring on less.
grade: stable # must be 'stable' to release into candidate/stable channels
confinement: strict # use 'strict' once you have the right plugs and slots
base: core18

icon: source/res/icon.png

apps:
  hanoi-tower:
    command: qt5-launch opt/hanoi-towers/bin/hanoi-towers
#    desktop: usr/share/applications/desc.desktop
    plugs: [desktop, home, opengl, x11, wayland]


parts:
  hanoi-tower:
    plugin: qmake
    source: source/
    build-packages:
      - qtdeclarative5-dev
    stage-packages:
      # Here for the plugins-- they're not linked in automatically.
      - libqt5gui5
      - libqt5qml5
      - libqt5quick5
      - qml-module-qtquick2
      - qml-module-qtquick-dialogs
      - qml-module-qtquick-controls
      - qml-module-qtquick-controls2
      - qml-module-qtgraphicaleffects
      - qml-module-qtquick-extras

after: [qt5conf] # A wiki part

actually here is the package collected in 18 04

After analyzing this problem, I came to the conclusion that the most likely error is in core 18
I really hope for your help

pollinate missing from core18 snap

Initial entropy can be low in cloud environments for which we have the pollinate package. I would like to see it added to the core18 snap.

Where is the licensing information?

When built, core18 has many licenses when scanned, but the source in this repo has no licenses. Are the licenses being inherited for "snap core" in some way? Thanks

mknod: /home/ubuntu/core18/parts/boostrap/install/dev/null: Operation not permitted

I'm trying to build core18 on a RasPi with Ubuntu 20.04. I'm no expert, but I think multipass might be getting angry due to unpriviledged container issues. To get around this issue: launch failed: CPU does not support KVM extensions., I use the SNAPCRAFT_BUILD_ENVIRONMENT=host env variable.

[ -e /home/ubuntu/core18/parts/boostrap/install/dev/null ] || mknod -m 666 /home/ubuntu/core18/parts/boostrap/install/dev/null c 1 3
mknod: /home/ubuntu/core18/parts/boostrap/install/dev/null: Operation not permitted
make: *** [Makefile:22: install] Error 1
Failed to run 'make install DESTDIR=/home/ubuntu/core18/parts/boostrap/install' for 'boostrap': Exited with code 2.
Verify that the part is using the correct parameters and try again.

Not really sure how to remediate this. Thoughts?

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.