SSM creeping into container

I have an odd issue. I have a host (ubuntu 24.04) as an AWS EC2 instance that runs the AWS Systems Manager (ssm-agent).
I’m running LXD and booted up the same Ubuntu 24.04 image. I installed the ssm-agent in the container too (for a project that requires the containers to have their own registration). When I went to login to the HOST machine using SSH via SSM, I was actually logging into the container. I had not registered the image yet. When I investigated I noticed that the container agent thought that the container was the same as the host and re-registered itself as the host.
I’m curious if anyone else has had this issue and was able to better isolate the container from the host?

name: nres-testing
description: ""
config: {}
devices:
  eth0:
    name: eth0
    network: nres-bridge
    type: nic
  root:
    path: /
    pool: nres-pool
    type: disk
used_by:
- /1.0/instances/nres-base-build
project: default

Hi!

LXD is no longer supported in this discussion forum

Instead, the Linux Containers project have moved to developing Incus. See how to migrate to Incus, which is a rather easy process.

The primary reason i’m using LXD is due to LXE so i can interface with Kubernetes. Incus may work with it but don’t know for how long.
I can try with incus to see if i have the same issues.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.