Lab 3.2

Hi @sergeizak,

To troubleshoot tool-specific errors it is recommended to visit the official page of the tool, which may provide installation guides, FAQs, troubleshooting tips, and possibly forums.

For the issue you are experiencing with the GPG key, there seems to be a workaround, posted in the LXC forum:
https://discuss.linuxcontainers.org/t/lxc-error-unable-to-fetch-gpg-key-from-keyserver/5434

Regards,
-Chris

Hi @chrispokorni ,

I'm on the step where you start the application on the container:

student@ubuntu:~$ lxc-start -n unpriv-cont-user -d

I am getting the following error message:
lxc-start: unpriv-cont-user: lxccontainer.c: wait_on_daemonized_start: 842 Received container state "ABORTING" instead of "RUNNING"
lxc-start: unpriv-cont-user: tools/lxc_start.c: main: 330 The container failed to start
lxc-start: unpriv-cont-user: tools/lxc_start.c: main: 333 To get more details, run the container in foreground mode
lxc-start: unpriv-cont-user: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriority option
s

I googled the issue and read through the following threads but the solutions are either personalized or incomplete:
https://discuss.linuxcontainers.org/t/error-with-fresh-ubuntu-18-04-container/3185/5
https://github.com/lxc/lxc/issues/3016
https://github.com/lxc/lxd/issues/5606

The prior commands were:
echo lxc.idmap = g 0 231072 65536 >>~/.config/lxc/default.conf
cat ~/.config/lxc/default.conf
sudo reboot
lxc-create -t download -n unpriv-cont-user

I don't see any log files in /var/log/lxc.

cat /var/log/syslog | grep unpriv doesn't return anything

The output of cat /etc/os-release | grep VER is:

Hi I am encountering quite the same issue:
lxc-start -n unpriv-cont-user -d
lxc-start: unpriv-cont-user: lxccontainer.c: wait_on_daemonized_start: 842 Received container state "ABORTING" instead of "RUNNING"
lxc-start: unpriv-cont-user: tools/lxc_start.c: main: 330 The container failed to start
lxc-start: unpriv-cont-user: tools/lxc_start.c: main: 333 To get more details, run the container in foreground mode
lxc-start: unpriv-cont-user: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriority options

lxc-start -n unpriv-cont-user --logfile=junk1.log --logpriority DEBUG

lxc-start unpriv-cont-user 20201005231613.604 ERROR network - network.c:lxc_create_network_unpriv_exec:2178 - lxc-user-nic failed to configure requested network: cmd/lxc_user_nic.c: 1296: main: Quota reached

Hi Chris...I am using GCP VM as advised in the lab guide please.

Thanks...Dhanesh

I resolved the below error by using the correct username when configuring lxc-usernet file.
In the documentation the line is to add the "student" string, but in practice my username was not "student". By checking the logfile resulted, noticed the problem came from the networking part and figured out the user name issue in the lxc-usernet file.

lxc-start: unpriv-cont-user: lxccontainer.c: wait_on_daemonized_start: 842 Received container state "ABORTING" instead of "RUNNING"
lxc-start: unpriv-cont-user: tools/lxc_start.c: main: 330 The container failed to start
lxc-start: unpriv-cont-user: tools/lxc_start.c: main: 333 To get more details, run the container in foreground mode
lxc-start: unpriv-cont-user: tools/lxc_start.c: main: 336 Additional information can be obtained by setting the --logfile and --logpriority

Logging was performed with:
lxc-start -n unpriv-cont-user --logfile=junk1.log --logpriority DEBUG
(thanks dhnijsure )

Hello,

the next step is giving me the error bellow.

student@ubuntu:~$ sudo lxc-start -n priv-cont -d
lxc-start: priv-cont: tools/lxc_start.c: main: 268 No container config specified

Did anyone face this issue?

@RaulSouza said:

@RaulSouza said:
Hello,

the next step is giving me the error bellow.

student@ubuntu:~$ sudo lxc-start -n priv-cont -d
lxc-start: priv-cont: tools/lxc_start.c: main: 268 No container config specified

Did anyone face this issue?

After some search, found a suggestion to add the parameter [-f] to specify the config file at [https://stackoverflow.com/questions/62594865/lxc-startno-container-config-specified]

however, after trying that, i'm facing the error bellow.

student@ubuntu:~$ sudo lxc-start -n priv-cont -d -f /home/student/.config/lxc/default.conf --logfile=junk1.log --logpriority DEBUG
lxc-start: priv-cont: lxccontainer.c: wait_on_daemonized_start: 859 Received container state "ABORTING" instead of "RUNNING"
lxc-start: priv-cont: tools/lxc_start.c: main: 308 The container failed to start
lxc-start: priv-cont: tools/lxc_start.c: main: 311 To get more details, run the container in foreground mode
lxc-start: priv-cont: tools/lxc_start.c: main: 313 Additional information can be obtained by setting the --logfile and --logpriority options

attached is the log file created during the execution. Please, could anyone have a look at that? Thanks in advance.

also tried to create the default.conf file under /root with root permissions, same behavior

Thank you very much.

Hi again.

Reviewed steps, and realized I've created the privileged container with wrong name.

after recreate with the command:
[student@ubuntu:~$ sudo lxc-create -t download -n priv-cont -- --keyserver hkp://keyserver.ubuntu.com]

the container start ran fine.
[student@ubuntu:~$ sudo lxc-start -n priv-cont -d]

Hi Chris,

Thanks for the feedback, already found the mistake (was a typo). Anyways, here it is the requested.

Regards,
Raul.

student@ubuntu:~$ cat /etc/subuid
ubuntu:100000:65536
student:165536:65536

student@ubuntu:~$ cat /etc/subgid
ubuntu:100000:65536
student:165536:65536

student@ubuntu:~$ cat /etc/lxc/lxc-usernet
# USERNAME TYPE BRIDGE COUNT
student veth lxcbr0 10

student@ubuntu:~$ cat ~/.config/lxc/default.conf
lxc.net.0.type = veth
lxc.net.0.link = lxcbr0
lxc.net.0.flags = up
lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx
lxc.idmap = u 0 165536 65536
lxc.idmap = g 0 165536 65536

student@ubuntu:~$ ll ~/.config/lxc/default.conf
-rw-rw-r-- 1 student student 162 Oct  3 22:23 /home/student/.config/lxc/default.conf