mountall | Mountall enhancements for ZFS on Linux | SSH Utils library

first of all, you don't want to install the "snap" package, as it is not related to "snapd". Secondly, myself stumbled across this issue of installing snapd within a docker container: TLDR; Running snapd that way is currently not supported.

But that question has been asked already at the snapcraft forums. One of snapd's dependencies is systemd and the snapd-service isn't properly initialized without a reboot or relogin. That is the required procedure according to the documentation across all distributions, but obviously isn't an option within docker.

At least this open question replicates your question most: unable-to-install-snapcraft-snap-in-docker-image-ubuntu-19-10

And Evan at the snapcraft forum here posted an approach, that I couldn't get to work either.

The only approach that might work is similar to running docker inside of docker, i.e.:

• install snapd on the docker host
• mount the snapd-socket at runtime into the container that has snapd installed.

But same warnings/side-effects apply as they do to running docker-in-docker.

sudo stop/start/restart service name worked for me, example:

sudo stop menuserver

As far as the VM is concerned, it looks like Jenkins is indeed running (based on the output from netstat and the list of running services):

tcp6 0 0 :::8081 :::* LISTEN 17917/java

Jenkins is a java application, and hence the process might only show up as java.

It look like you're trying to access the service through the instance's public IP and port. The Google Compute Engine (GCE) firewall might be blocking this, since by default all incoming ports from external IPs in GCE VMs are blocked.

If your goal is to access this port on this machine from any public IP, you can follow these steps to grant access:

Lubuntu 16.04 comes with systemd by default. At some point you must have started up a jenkins instance in docker - it's hard to tell exactly what started the process initially. However, systemd would be what is currently causing it to start. In order to stop it from running, run the following commands:

systemctl status docker <- Find out of systemctl thinks docker is running.

It'll likely show something like this:

● docker.service - Docker Application Container Engine Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2017-05-21 22:59:46 EDT; 1 day 17h ago Docs: http://docs.docker.com Main PID: 1314 (dockerd-current) Tasks: 14 (limit: 8192) CGroup: /system.slice/docker.service └─1314 /usr/bin/dockerd-current --add-runtime oci=/usr/libexec/docker/docker-runc-current --default-runtime=oci --containerd /run/containerd.sock --exec-opt native.cgroupdriver=systemd --userland-proxy-path=/usr/libexec/docker/docker-proxy-current --selinux-enabled --log-driver=journald

To stop it, run systemctl stop docker and then systemctl disable docker. As a last resort if this doesn't work, you can run systemctl mask docker.

I never did figure it out, but instead went with this tutorial and set up my service with pm2.

You need to to do:

The logstash in the container is not run as a system service, the entrypoint in the image will start a process and will keep the container up until this process ends or fails.

If you do a docker top 12 it will show the logstash process running (probaly alone) in the container.

To stop the lostash, you need to stop the container with docker stop 12, and later when you need to start it again you can run docker start 12, it will work as long you set the containers name as 12 when you create or first run it.

Docker Start help: https://docs.docker.com/engine/reference/commandline/start/

Docker stop help: https://docs.docker.com/engine/reference/commandline/stop/

Docker create: https://docs.docker.com/engine/reference/commandline/create/