You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Description of changes:
Upgrading Go Dependencies host-ctr with containerd going to 1.6.23 which will align with #3362
Upgrades containerd code dependencies to v1.6.23
Upgrades opencontainers/runtime-spec to one used by containerd v1.6.23
Testing done:
Launched instance and it connects without issue
bash-5.1# systemctl status host-containers@admin
● host-containers@admin.service - Host container: admin
Loaded: loaded (/x86_64-bottlerocket-linux-gnu/sys-root/usr/lib/systemd/system/host-containers@.service; enabled; preset: enabled)
Active: active (running) since Mon 2023-08-28 15:17:57 UTC; 5min ago
Main PID: 1145 (host-ctr)
Tasks: 9 (limit: 9335)
Memory: 40.8M
CPU: 273ms
CGroup: /system.slice/system-host\x2dcontainers.slice/host-containers@admin.service
└─1145 /usr/bin/host-ctr run --container-id=admin --source=328549459982.dkr.ecr.us-west-2.amazonaws.com/bottlerocket-admin:v0.10.2 --superpowered=true --registry-config=/etc/host-containers/host-ctr.toml
Aug 28 15:18:00 ip-192-168-187-145.us-west-2.compute.internal host-ctr[1145]: time="2023-08-28T15:18:00Z" level=info msg="pulled image successfully" img="ecr.aws/arn:aws:ecr:us-west-2:328549459982:repository/bottlerocket-admin:v0.10.2"
Aug 28 15:18:00 ip-192-168-187-145.us-west-2.compute.internal host-ctr[1145]: time="2023-08-28T15:18:00Z" level=info msg="unpacking image..." img="ecr.aws/arn:aws:ecr:us-west-2:328549459982:repository/bottlerocket-admin:v0.10.2"
Aug 28 15:18:08 ip-192-168-187-145.us-west-2.compute.internal host-ctr[1145]: time="2023-08-28T15:18:08Z" level=info msg="tagging image" img="328549459982.dkr.ecr.us-west-2.amazonaws.com/bottlerocket-admin:v0.10.2"
Aug 28 15:18:08 ip-192-168-187-145.us-west-2.compute.internal host-ctr[1145]: time="2023-08-28T15:18:08Z" level=info msg="Container does not exist, proceeding to create it" ctr-id=admin
Aug 28 15:18:08 ip-192-168-187-145.us-west-2.compute.internal host-ctr[1145]: time="2023-08-28T15:18:08Z" level=info msg="container task does not exist, proceeding to create it" container-id=admin
Aug 28 15:18:08 ip-192-168-187-145.us-west-2.compute.internal host-ctr[1145]: time="2023-08-28T15:18:08Z" level=info msg="successfully started container task"
Aug 28 15:18:08 ip-192-168-187-145.us-west-2.compute.internal host-ctr[1145]: Created symlink /root/.config/systemd/user/admin.target.wants/getty@tty0.service, pointing to /etc/systemd/user/getty@.service.
Aug 28 15:18:08 ip-192-168-187-145.us-west-2.compute.internal host-ctr[1145]: Created symlink /root/.config/systemd/user/admin.target.wants/serial-getty@ttyS0.service, pointing to /etc/systemd/user/serial-getty@.service.
Aug 28 15:18:08 ip-192-168-187-145.us-west-2.compute.internal host-ctr[1145]: Created symlink /root/.config/systemd/user/admin.target.wants/sshd.service, pointing to /etc/systemd/user/sshd.service.
Aug 28 15:18:08 ip-192-168-187-145.us-west-2.compute.internal host-ctr[1145]: Startup finished in 14ms.
bash-5.1# systemctl status host-containers@control
● host-containers@control.service - Host container: control
Loaded: loaded (/x86_64-bottlerocket-linux-gnu/sys-root/usr/lib/systemd/system/host-containers@.service; enabled; preset: enabled)
Active: active (running) since Mon 2023-08-28 15:17:57 UTC; 6min ago
Main PID: 1146 (host-ctr)
Tasks: 9 (limit: 9335)
Memory: 24.5M
CPU: 513ms
CGroup: /system.slice/system-host\x2dcontainers.slice/host-containers@control.service
└─1146 /usr/bin/host-ctr run --container-id=control --source=328549459982.dkr.ecr.us-west-2.amazonaws.com/bottlerocket-control:v0.7.3 --superpowered=false --registry-config=/etc/host-containers/host-ctr.toml
Aug 28 15:18:09 ip-192-168-187-145.us-west-2.compute.internal host-ctr[1146]: 2023-08-28 15:18:09 INFO [Registrar] Starting registrar module
Aug 28 15:18:09 ip-192-168-187-145.us-west-2.compute.internal host-ctr[1146]: 2023-08-28 15:18:09 INFO [EC2Identity] no registration info found for ec2 instance, attempting registration
Aug 28 15:18:09 ip-192-168-187-145.us-west-2.compute.internal host-ctr[1146]: 2023-08-28 15:18:09 INFO [EC2Identity] EC2 registration was successful.
Aug 28 15:18:09 ip-192-168-187-145.us-west-2.compute.internal host-ctr[1146]: 2023-08-28 15:18:09 INFO [CredentialRefresher] credentialRefresher has started
Aug 28 15:18:09 ip-192-168-187-145.us-west-2.compute.internal host-ctr[1146]: 2023-08-28 15:18:09 INFO [CredentialRefresher] Starting credentials refresher loop
Aug 28 15:18:09 ip-192-168-187-145.us-west-2.compute.internal host-ctr[1146]: 2023-08-28 15:18:09 INFO EC2RoleProvider Successfully connected with instance profile role credentials
Aug 28 15:18:09 ip-192-168-187-145.us-west-2.compute.internal host-ctr[1146]: 2023-08-28 15:18:09 INFO [CredentialRefresher] Next credential rotation will be in 30.699995224283334 minutes
Aug 28 15:18:10 ip-192-168-187-145.us-west-2.compute.internal host-ctr[1146]: 2023-08-28 15:18:10 INFO [amazon-ssm-agent] [LongRunningWorkerContainer] [WorkerProvider] Worker ssm-agent-worker is not running, starting worker process
Aug 28 15:18:10 ip-192-168-187-145.us-west-2.compute.internal host-ctr[1146]: 2023-08-28 15:18:10 INFO [amazon-ssm-agent] [LongRunningWorkerContainer] [WorkerProvider] Worker ssm-agent-worker (pid:15) started
Aug 28 15:18:10 ip-192-168-187-145.us-west-2.compute.internal host-ctr[1146]: 2023-08-28 15:18:10 INFO [amazon-ssm-agent] [LongRunningWorkerContainer] Monitor long running worker health every 60 seconds
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.
- Upgrades containerd code dependencies to v1.6.23
- Upgrades opencontainers/runtime-spec to one used by containerd v1.6.23
Signed-off-by: Matthew Yeazel <yeazelm@amazon.com>
Something seems off about that go.sum diff, but if Go can now clean up dependencies better, or if updated packages got rid of old duplicates, that is awesome. Love any time we see the removed line count greater than the added line count. Testing should confirm if everything is good.
Something seems off about that go.sum diff, but if Go can now clean up dependencies better, or if updated packages got rid of old duplicates, that is awesome. Love any time we see the removed line count greater than the added line count. Testing should confirm if everything is good.
I ran go mod tidy and I wonder if folks hadn't done that in a while, many of these seem to be quite old dependencies. Or maybe Go is just better at purging the only ones. Everything seems to work great, so I think its ending in the right place.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue number: #3172
Closes #
Description of changes:
Upgrading Go Dependencies host-ctr with
containerdgoing to 1.6.23 which will align with #3362Testing done:
Launched instance and it connects without issue
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.